3 ms·

Very well written and a joy to read. Yes, IDEs of the future will not look like those we have today. I too started with Cursor and similar VS Code enhanced IDE

Very well written and a joy to read. Yes, IDEs of the future will not look like those we have today. I too started with Cursor and similar VS Code enhanced IDEs. And ended up using Claude Code. And realised my terminal is more important for me now. So I migrated from iTerm to Ghostty (faster, lighter, more modern), Tmux and Tmuxinator, and NeoVim! Because I just cat/bat files and occasionally edit a file, if at all. Claude Code does the heavy lifting, I write specs and prompts, in NeoVim or Emacs. And I am loving my workflow. I too use Claude Code for more then just generating code. Whenever I need to rewrite a config file (for zsh, neovim, ghostty, etc), I start Claude code and assign the task to do it. It will do the changes and even refactor my settings file in a few minute. Lastly, I use it to ask questions about my codebase, refactor code, let it document my code, even make meaningful commits. Pure awesomeness.

indigodaddy 1y ago
Will CC automatically backup these personal configs you are talking about, say .zshrc, before making changes?
- AnotherGoodName 1y ago
  It’s a feature of the ide but pretty much all of them have an option for ais to only change code via a merge and review process. It’s not the ai changing directly, it’s heres a diff; accept, change, discard process after the prompt. Past there the ides usually have a local history and yiu can also use git.
- submeta 1y ago
  I keep track of all my config files via git. And after any change I make a commit (ask the tool to do that).
alwillis 1y ago
> Lastly, I use it to ask questions about my codebase, refactor code, let it document my code, even make meaningful commits. I've found that CC writes really good commits; I added info about Conventional Commits [1] to the CLAUDE.md file with a few examples. [1]: https://www.conventionalcommits.org/en/v1.0.0/#summary https://www.conventionalcommits.org/en/v1.0.0/#summary
- submeta 1y ago
  Nice! Thanks for sharing.
- danielbln 1y ago
  It's also quite good at setting up PRs: "use GitHub CLI to create a PR, keep the desc tights, no purple prose, no emojis" and you get solid PR ready to go
qn9n 1y ago
I similarly migrated to Ghostty but have found the built-in tabs and panes more than enough so haven't required tmux.

indigodaddy 1y ago

Will CC automatically backup these personal configs you are talking about, say .zshrc, before making changes?

AnotherGoodName 1y ago
It’s a feature of the ide but pretty much all of them have an option for ais to only change code via a merge and review process. It’s not the ai changing directly, it’s heres a diff; accept, change, discard process after the prompt. Past there the ides usually have a local history and yiu can also use git.
submeta 1y ago
I keep track of all my config files via git. And after any change I make a commit (ask the tool to do that).

alwillis 1y ago

> Lastly, I use it to ask questions about my codebase, refactor code, let it document my code, even make meaningful commits. I've found that CC writes really good commits; I added info about Conventional Commits [1] to the CLAUDE.md file with a few examples. [1]: https://www.conventionalcommits.org/en/v1.0.0/#summary https://www.conventionalcommits.org/en/v1.0.0/#summary

submeta 1y ago
Nice! Thanks for sharing.
danielbln 1y ago
It's also quite good at setting up PRs: "use GitHub CLI to create a PR, keep the desc tights, no purple prose, no emojis" and you get solid PR ready to go

qn9n 1y ago

I similarly migrated to Ghostty but have found the built-in tabs and panes more than enough so haven't required tmux.