←back to thread

757 points rcchen | 1 comments | | HN request time: 0.207s | source
Show context
submeta ◴[] No.44537605[source]
I went from Emacs to VS Code, then to Cursor, next to Claude Code, which is so good that I feel like I am having half a dozen junior devs at my fingertips, 24/7.

Since Claude Code is cli based, I reviewed my cli toolset: Migrated from iTerm2 to Ghostty and Tmux, from Cursor to NeoVim (my God is it good!).

Just had a 14h workday with this tooling. It’s so good that I complete the work of weeks and months within days! Absolutely beast.

At this point I am thinking IDEs do not reflect the changing reality of software development. They are designed for navigating project folders, writing / changing files. But I don’t review files that much anymore. I rather write prompts, watch Claude Code create a plan, implement it, even write meaningful commit messages.

Yes I can navigate the project with neovim, yes I can make commits in git and in lazygit, but my task is best spent in designing, planning, prompting, reviewing and testing.

replies(9): >>44537772 #>>44537863 #>>44537970 #>>44538082 #>>44538227 #>>44538278 #>>44538704 #>>44538731 #>>44539595 #
1. apwell23 ◴[] No.44538082[source]
yes vibecoding is addicting like that. but if you are not reviewing any code and simply vibing then in my expreience you'll eventually get stuck in "its still not working" loops beause you have no other context or insight to provide it other than that. Then you have either accept what you have or throw the whole thing out and/or actually read the code . kind of rules out last option because code is now just too far gone with too many special cases hardcoded because AI sucks at abstraction or real software engineering.