News for hackers. Stuff that matters.
Re:Plan Mode Is Dead by senordevnyc on Saturday September 26, 2026 @11:36AM (#49857547)
I completely agree with everything you’ve said, in the pre-AI world. Now, I’m not so sure.

When I worked at a big tech company on a large codebase (tens of millions of LOC across dozens of repos), it was extremely common to work on something in an area of the codebase I had zero familiarity with, and due to turnover, no one else at the company did either. As you say, docs were frequently missing or out of date.

However, with some effort over a couple hours, I could make a LOT of progress in understanding the history of the code. Every commit and PR were linked to JIRA tickets, most had eng design docs with comments, slack discussions, etc. I could step through the git history and watch the code change, alongside the artifacts of the human discussion and decisions that led to the changes. It wasn’t perfect, but I could make tremendous progress. Now, this was a remote company with pretty strong culture around using JIRA, design docs with review, etc. Probably the biggest gap was meeting transcripts.

Today, an agent can chew through years of history and artifacts on a large codebase in a half hour, documenting as it goes, and have way better understanding of it than I ever will.

It’s true that an agent can’t hold all of that in its head at once without context rot (though this is improving every year), but neither can any human!

If your goal is understanding how to do something, why something was done, why something wasn’t done, etc, and the codebase is large, mature, and extremely well-“artifacted”, I’m not at all convinced that you’re better off asking Bob who has worked on this section of the codebase for a decade than just asking a really good frontier-level agent. Maybe, but it feels like that won’t be true much longer.

Re:Plan Mode Is Dead by maccard on Saturday September 26, 2026 @12:16PM (#49857952)
> Today, an agent can chew through years of history and artifacts on a large codebase in a half hour, documenting as it goes, and have way better understanding of it than I ever will.

At my last job we worked in a large, but publicly available code base. My experience was that just giving an agent the prompt to look at area X to figure out how it works would use up half or more of the context window. And that was thrown away every time we started again. We had docs, agent generated overviews but the agents still filled their context windows way too quickly to actually really be any use.

Re:Plan Mode Is Dead by aDyslecticCrow on Sunday September 27, 2026 @03:44PM (#49870125)
I have a hard time finding concrete examples that does not breach contract of dox me.

I feel like this issue goes beyond a single large legacy codebase. It can go beyond how the code works into what the code does. How should a thing behave may itself be institutional knowledge only Bary that was involved in the design process still remembers.

Pointing an agent at a problem in one codebase to write a patch can work quite well. But what do i do when the problem is either in the tool, the database, or the two API layers between? You may not even have the code for half of it as it's part of another department or externally purchased solution.

Bary would know, or know who to talk to, or dig up a PowerPoint slide he's been working on to explain it.