upvote
I found that keeping my prompts small and incremental and reviewing the output at each step helps a lot both with keeping my skills sharp and keeping knowledge of the code. It is interesting that I actually learn new tricks from LLM generated code and keep it in check when it goes overengineering.

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.

reply
I divide projects in "care code" and "care result". I am buiding random tools all the time for which I dont check the code. For my long term project I do check the code.

This is the best I came with so far, but I have to admit how slow my main projects move, if at all.

reply
Yeah I’ve tended to align with this split as well. I will say that there has been a huge productivity boost from making these random throwaway tools composable because then I can chain them together via old-fashioned shell wizardry or having agents use them. Also have found it more repeatable and reliable to ask an agent to build me a tool to do a task (above some complexity threshold) vs asking it to do the task directly.
reply
I think I have the same experience, both good and bad. Smaller tighter feedback loops are like smaller PRs I review but at a much slower overall speed multiplier than straight vibing. Additionally I found I can use smaller context and even sometimes smaller models and get results back faster, but I must be more hands-on guiding things.
reply
I can attest to the first part. I think I've gone on record elsewhere in comments on HN that I much prefer using an LLM in a "sage" mode, where it functions more like a tutor/mentor than between me and the work. This has accelerated learning and, like you, I've learned new tricks this way.

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.

reply
There is still value IMO in creating atomic tickets for systems where humans are in the loop. Building a new UI experience? Have each component at minimum be it's own ticket. Maybe theres additional layers where you can break it down, scaffolding, skeletons, etc. For human led teams where AI is just making the code and helping with design decisions I think this is still the way to go for the bulk of the work. Can AI do everything soup to nuts? Sure but nobody is going to review that well and you can't revert part of it without taking out the whole change.

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.

reply
> I can turn a flesh-and-blood Junior/Intern developer into full independent developer I can trust with more complex tasks. I can't do that with AI.

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.

reply
> I agree with the author we're in a weird moment

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.

reply
Definitely agree. AI being so-so at the moment is a strength; it's just capable enough to be useful, but makes enough mistakes that we must develop those new BPs. I wish tech management would slow down and give us time to develop these new practices. It would certainly make AI less polarizing.
reply
It is a weird state.

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

reply
I love coding and I love teaching. I greatly enjoy working with novices because I can teach them; but I’m not a manager. Agentic stuff sounds like my nightmare: little of the coding, none of the teaching, all of the managing. Ugh.
reply
>> However I can turn a flesh-and-blood Junior/Intern developer into full independent developer I can trust with more complex tasks. I can't do that with AI.

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.

reply
When enraged_camel lies through his teeth like this it's not to try to convince anyone who has experience. It's to catch those who don't. This site used to be a place where developers helped each other out and that's still true to some extent. But for a lot of greedy people on here lately, you are no longer an equal. You are the mark.
reply
It's not a lie in the sense that those individual developers cannot match the KLOC/day output.
reply
It's always a guy saying "I know some really smart dudes, and AI is better than them," and not "I'm a really smart dude, and AI is better than me."

Curious...

reply
I'm a really smart dude, and AI is better than me.
reply
I agree with your comment but I also think an important factor to consider is that AI is also capable of producing good quality documentation, diagrams and explanations of the code that it produces.

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.

reply
The ideal manager sacrificed their immediate day to day skills to mentor a team in those skills, thus increasing the overall velocity while the manager's individual velocity atrophied. Both AI and outsourced workers are run by companies provide a service for a fee, but refuse to take any responsibility for the output. If their work is delivered broken your only recourse is to resubmit the work and pay them again.

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.

reply
Yes, but the problem is that you get a firehouse of information that is difficult to manage.

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

reply
Is it? Almost every comment I read from them is complete nonsense word salad.
reply
You're not wrong, but even if you were, no... reading documentation, even good documentation, is not enough to prevent skill atrophy.

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.

reply
> Five years ago it was common knowledge on HN that moving away from the code (like taking a management position) atrophied your programming skills. The routine suggestion was to get your hands dirty again.

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.

reply