I'm opening VSCode less and less every day
21–29 of 29 posts
Re: I'm opening VSCode less and less every day
#22Re: I'm opening VSCode less and less every day
#23Is this something people widely vary on? I suspect a lot of people are not like me given that I do see people saying things such as “I rarely use my ide/editor any more” with AI, hence my question to you. Maybe I’m just bad at keeping the code base all in my head.
I do agree with you that I feel that I am coding less myself and I do miss that for sure. But the job demands otherwise.
Re: I'm opening VSCode less and less every day
#24Genuine question - do you feel that you understand a code change well enough by only viewing diffs, enough to push the Claude code as “your own”? I can see this for some types of PRs but for anything that is relatively complex or touches multiple files, I personally have to open an editor and navigate through the code paths to really grok if an AI’s (or a human’s for that matter) change is correct. Is this something…
Re: I'm opening VSCode less and less every day
#25Re: I'm opening VSCode less and less every day
#26One thing I would note is, I build AI Agents as my job these days, if an agent process is complex, its impossible to write even 90% working code via LLM's.
Re: I'm opening VSCode less and less every day
#27Genuine question - do you feel that you understand a code change well enough by only viewing diffs, enough to push the Claude code as “your own”? I can see this for some types of PRs but for anything that is relatively complex or touches multiple files, I personally have to open an editor and navigate through the code paths to really grok if an AI’s (or a human’s for that matter) change is correct. Is this something…
Re: I'm opening VSCode less and less every day
#28This brought an interesting philosophical question: do you enjoy coding itself? Or something else? If you enjoy coding itself IDE or AI agent doesn’t really matter.
Re: I'm opening VSCode less and less every day
#29Don't you need to look at the code you want to change in order to direct the AI in what you want to do, or are you simply telling it to make a feature and then looking at the changes it makes?
1. Start a session.
2. Grill my requirements (I use Matt Pocock's skills).
3. Write an ADR, then either start implementing or separate into pieces.
4. Review the code on pyor.review, compared to Github, Pyor allows me to categorize the files and changes then review the important stuff and skim the noise it identifies.
5. Since I can do local reviews with Pyor, I can do that with Claude and feed back my comments to be addressed without it going to Github first.
6. Create a PR then merge it.