but I can say that, anyone experienced will notice how you really can't just "let them loose" on the codebase because they'll lose context, not understand the architecture, not have good vision/ideas about the codebase etc.

so I'm bottlenecked by following the code generation and then having to review and respond

and there's so many times where I go "wait but can't we just do x?" and then the model goes, "oh let me see.. yes we can"

if you were to just use agents w/o looking at code you'd have complete spaghetti in no time

maybe the future is that you embrace the spaghetti and just treat code as a black box where all you care about is the input/output

but my intuition tells me that it's not really viable yet. you'll take many steps forward and many steps back.

But honestly, the practice of programming then was not dramatically different from programming in, say, the mid-2010s. Obviously we leaned more heavily on the official documentation, and tbf, a lot of the docs were provided in PDFs, which is probably the single worst way to provide documentation.

Sometimes, the docs were provided as collections of papers bound together by a "spine". This is actually a wonderful documentation format because our brains can associate physical locations in the physical media with specific pieces of information.

(this is the oldest I have ever been in my entire life)

Most people people here do not code. They wish they do, but they don't.