Live data from Hacker News

I'm opening VSCode less and less every day

news.ycombinator.com

21–29 of 29 posts

Re: I'm opening VSCode less and less every day

#22
I still open Neovim, or yazi at the very least, just as much as before, gotta see what OpenCOde has been up to or it will slop the whole NixOS configuration to hell while you are looking away. And that is for my personal declarative OS set up being homeless and been on an unlucky since right before COVID but had the ability to learn all this niche crap and now LLMs make it possible to keep learning in ever less stable conditions. You are being reckless as all hell with the code you with take the `git blamne` for and could hurt more than just yourself if you are being as careless as this suggests...

Re: I'm opening VSCode less and less every day

#23
Genuine 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 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

#24

Genuine 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…

I would really like to know how people work on anything more complicated than a single page website without using an IDE/Editor any more - in my experience, AI is just not up to the task of managing multi-file projects without me having a very sharp eye on what it does.

Re: I'm opening VSCode less and less every day

#26
++1, I miss writing code.... around 60-65% of my code is written by Antigravity now. On VS Code, I had similar thoughts earlier, but after Antigravity 2.0, they have separated IDE with Agent Manger. So from now on, I am back to VS Code as my primary IDE.

One 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

#27

Genuine 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…

Yeah, I use VSCode a lot less now, even for code reviews, I built my own code reviewer that's better than Github IMO. I no longer use VSCode or Github, I use Claude to produce the code and use https://pyor.review to review the code, same thing when I review my teammates' PRs.

Re: I'm opening VSCode less and less every day

#28
post #25

This 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.

Good question, If you enjoyed coding itself, you'll have a hard time now, but if you enjoy building stuff, you'll thrive in this era.

Re: I'm opening VSCode less and less every day

#29

Don'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?

That's how I code nowadays:

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.

Post reply on HN