Remix.run Logo
▲ Teever a day ago

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.

▲JamesLeonis a day ago | parent | next [-]

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.

▲trueno 2 hours ago | parent | prev | next [-]

AI produces some of the worst documentation i've ever seen. It's a new class of docs that are borderline unapproachable for humans. It's natural at this point to just lose focus/interest entirely when reading AI produced docs

▲rbn3 a day ago | parent | prev | next [-]

I‘d say currently AI is much much better at code than documentation though. It constantly keeps doing this thing where it references things the reader cannot possibly know yet. As if the documentation was written with the assumption of the reader having all context that lead to the writing of the docs in mind already.

▲matltc a day ago | parent | prev | next [-]

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

▲Rumple22Stilk a day ago | parent | prev [-]

Is it? Almost every comment I read from them is complete nonsense word salad.

▲lkjdsklf a day ago | parent [-]

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.

▲seanw444 a day ago | parent [-]

The note taking analogy is the best one I can think of. It's directly analogous. Plenty of people have heard of "writing notes by hand builds stronger links in your brain" in the context of schooling, but when it comes to programming, they can't draw the painfully obvious parallel.

Really the goal is to have these models completely replace software engineers altogether. Skill atrophy isn't a concern when you don't employee devs whose skills need to be prevented from atrophying. A lot of devs also can't draw this obvious conclusion.

It's weird feeling like the odd man out with these two conclusions on the matter. But software devs are stuck in the fantasy of "this makes me a 1000x engineer and it's a tool that works for me, for my benefit". Which, sure, when you use it as a research tool, I can agree. Agentic code generation, if it doesn't outright replace engineers, will be seen as the tiktokification of programming, and its effects will become obvious, hopefully in the not-too-distant future.