I'm biased (I'm a dev advocate at JetBrains), but I also still actively write code and use PhpStorm almost daily.
Yes, we're writing less code, but the job of "a programmer" has always been about so much more than _writing_ code. It's about code reviews, QA, debugging, discovery, and maintenance; much more than the "writing" part. Anyone with production code will agree, I think: the writing part is the easy part. That's where I still very much prefer a proper IDE over a text editor or terminal. I want easy code navigation, I want proper static analysis without relying or waiting on third party tools, I want a visual overview of changes that happened. I want to stay in charge of whatever is writing my code. On top of that, I want my agents to have access to the tools that have made me the most productive developer for years.
> It's about code reviews, QA, debugging, discovery, and maintenance; much more than the "writing" part.
AI can do all of that quite well. If you take your hands off of the wheel, lean into it, start building systems for it, start figuring out where it goes wrong on your codebase and building systems to prevent that... you might get 10x more done. I do, and the results are generally better than anything I'd have coded by hand, because there was never enough time.
I don't look at or try to grok all changes, though. I couldn't get near as much done, otherwise, and I'm not convinced that 1 hr of me looking over it is better than 4 hrs of AI looking over it, and the AI is far cheaper. I look over the code, occasionally, to look for code that's objectively terrible, but I don't fix it directly - I use it as a test-case for improving my AI stack, to make it able to find and fix or prevent that class of terrible.
I probably spend 9 out of 10 credits on review and refinement, not writing fresh code. In spite of that, I'm still producing things way faster than I ever did by hand, with only a single $200/mo Codex plan.
I still keep my JetBrains' subscription, so that agents can use the MCP. I probably spend <5h per month in an IDE myself, though.
> much more than _writing_ code. It's about code reviews, QA, debugging, discovery, and maintenance;
Of course, but agents are also opening up new possibilities to do these jobs.
For example, you can do quick first code review with agent, or you can ask agent to add couple of print statements and debug the code until it figures out the issue, also for discovery, you can do discovery with agents and generate nice output with the details you want (although not accurate sometimes)
As a JetBrains user myself, whose organization cancelled the IntelliJ license recently, I can attest things I am doing inside IntelliJ is getting less and less. I am primarily using IntelliJ for code navigation at the moment, which is still the best one
Yes, we're writing less code, but the job of "a programmer" has always been about so much more than _writing_ code. It's about code reviews, QA, debugging, discovery, and maintenance; much more than the "writing" part. Anyone with production code will agree, I think: the writing part is the easy part. That's where I still very much prefer a proper IDE over a text editor or terminal. I want easy code navigation, I want proper static analysis without relying or waiting on third party tools, I want a visual overview of changes that happened. I want to stay in charge of whatever is writing my code. On top of that, I want my agents to have access to the tools that have made me the most productive developer for years.
Curious about your thoughts?