But that makes LLM speedup like 1.5x the manual-typing coding speed, vs 50-100x you can get if you vibe all the way.
I still use LLMs for troubleshooting, searching, codebase knowledge gathering, solution exploration, writing tests and documentation and whole-codebase changes and there the speedup is dramatic. However I don't feel I become a better developer for doing these kind of tasks without LLMs.
For documentation and tests though I feel I am slipping on reviewing the output because it is just so boring that I often "surrender" the task to the LLM which generates bloated tests and bloated docs.
This is the best I came with so far, but I have to admit how slow my main projects move, if at all.
As for the last part about bloat, I've started tinkering with prompts that attempt to minimize generated code output. I'd wager that having agents take a second or third pass to "prune" the output of the former would work too.
If you have a robust ticketing solution at your org just use it. Theres probably a baked in MCP. At work I use(d) JIRA (laid off, hmu w bay area or remote work), at home github issues are fine to a point then I use vikunja or openproject depending on the box its gonna live on.
If I was Junior in 2026 I would be breaking down work into the smallest components possible so that my understanding of the work was scoped and more importantly the inevitable AI sprawl would be similarly scoped (and easier to rein in/call out).
If you don't know how to break the work down ask for help. I wish I asked for help more earlier in my career.
To some extent, you can: better doc and better support scripts (linters, tests, infra as code, etc) do not replace a human being but it goes a long way toward improving your coding agent. Especially since many of those ad-hoc scripts wouldn't even have been written by hand in the first place. The cost/benefit ratio changes.
We're in the twilight zone, AI ain't there yet, neither are developers.
> where the Best Practices seemingly flipped
There will be new BPs when AI becomes real - for now it's enough to make sure open source AI gets there first.
> the AI talk mirrors the Outsourcing talk from the early 2000s. I have a terrible feeling we are going to learn these bitter lessons all over again.
Because of this and a lot more.
- You can't write code as fast or "good enough" as AI.
- Not writing code quickly atrophies your ability to do anything code related.
It seems to me like a giant bet on AI being able to replace software devs (and soon - other professions). And you're forced to participate in that bet if you want to stay a software dev.
Why not? Over the past 20 years I've worked with some incredibly smart and accomplished engineers, some of whom have single-handedly built complex products and services used by millions. And today none of them would come anywhere close to what frontier models are capable of.
Curious...
This has the potential to mitigate some of the atrophy that is well documented in management positions and perhaps for someone in such a position (be it managing people or AI) to review code better than they otherwise would.
This means we must be just as skilled as before AND manage these other inputs AND take responsibility for the overall deliverable. No wonder developers are burning out.
The recurring problem I see is that we have been given immense power but abdicated responsibility. That is understandable, given the marketing and packaging kf the tools as "agents" that do tasks end to end.
Reality is that you need like one or more specialists in devops (mlops? I think that's a thing) to implement a reliable pipeline. The parallel agent model has never worked for me, because I am a careful reviewer
https://www.reddit.com/r/ClaudeCode/comments/1y0yquc/they_pu...
Apologies for raw reddit link, old.reddit.com dead and I can't recall the thing to use now
There is literally decades of research into this at all levels of education. You absolutely "lose" skills that you don't practice and reading documentation is not the same skill as writing/reviewing code. Active learning vs passive learning.
It's the reason "note taking" was invented and we don't just sit there and listen to lectures.
It's pretty shocking how many supposedly smart people are just forgetting very basic things that are literally things you learn in middle school.
Yes, you're right. Moving away from the code would atrophy your programming skills, sort of, but if you're still involved with the code on a day-to-day basis, then you're not moving away from the code.
> AI-first folks will tell me I should see my new responsibility as being just such a manager over little agent kiddos running around
Yeah, I've never heard someone talk about it like that, but I'll assume that you have and just say that whoever you're listening to is nobody that knows what they're talking about. I've never seen anyone describe it like that, and you can safely not listen to them.
Which means if you're getting your information from people like that, you probably are very much misinformed, because I wouldn't trust anyone who said something like that to properly inform me.
The important thing to realize is: is somebody moving away from code and moving to non-code things, like a management position, or are they still involving themselves day to day with the code and just working with the code differently? And the disinformation that you've been fed seems to have polluted your way of thinking. I would go back and review where you got this information because, again, it's not a trustworthy source if they're talking about kiddos.