←back to thread

766 points rcchen | 1 comments | | HN request time: 0.214s | 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 #
rileymichael ◴[] No.44537970[source]
> It’s so good that I complete the work of weeks and months within days

and yet you're pulling 14 hour workdays..

replies(4): >>44538005 #>>44538087 #>>44538821 #>>44539337 #
jen729w ◴[] No.44538087[source]
Well you can't risk Claude quitting overnight. It forgets everything it did the day before and now you have to start over ... must ... finish ... tonight ... within ... context ... window.
replies(1): >>44539847 #
1. TeMPOraL ◴[] No.44539847[source]
Fortunately LLMs are stateless thus not affected by passage of time - your context stays exactly as it was while the tool maintaining it is running.

(Prompt caches are another thing; leaving it for the night and resuming the next day will cost you a little extra on resume, if you're using models via API pay-as-you-go billing.)