← sources

Giving your codebase entirely to the AI

source: reddit (reddit:ExperiencedDevs)published 2026-09-30 10:55ingested 2026-10-01 02:39

retained text

SWE for 20 years. I've seen plenty of posts about the soul-sucking prompt engineering some companies mandate now. Mine isn't one of those - AIs are a tool you are encouraged to use, but the output has to be understandable, human-reviewable, and you (as a dev) are still responsible for it and the consequences.

I think the difference is whether you give your codebase completely to the AI. If you treat the code the same way we treat assembler now, then that's what you do - you specify the *what*, and the AI completely handles the *how*, which leads to 5000-line pull requests, only reviewed by other AIs, and all that jazz. The problem comes when the AI *can't* do something, or you encounter a problem that a human needs to solve. Then you're faced with working out WTF a 1-million line codebase is actually doing *from scratch*, that wasn't even written by a human, probably with CxOs breathing down your neck. Good luck with that.

This decision assumes that AIs will always be able to solve the problem, of course. And maybe that's where we're all going, and writing (and understanding) actual code will become just as niche as assembler programming is now. But, given what I've seen of AI output and how nonsensical and daft it can be, we aren't there yet.

Unfortunately, it's not the devs who might end up maintaining it actually deciding where and how AI should be used. All that matters is *throughput*.

My company still keeps everything human-understandable, because a lot of people depend on the product working properly. That's unlikely to change in the next...year? 2 years? Who knows. But I really wonder where the *craftsmanship* of software engineering will go in 5 years time. Seeing what's happened even in the last 6 months, I have no idea what my long-term job prospects are.

document fetched 2026-10-01 00:28 · canonical https://reddit.com/r/ExperiencedDevs/comments/1wu1tzt/giving_your_codebase_entirely_to_the_ai