[jonator]

I’ve found a good counter to this is having agents visualize and explain the architecture of the system. Then I gain just enough context to figure out what I’m trying to accomplish.

Also, as always, a highly modular codebase is very important. If I only have to reason about a single module then I don’t have to have full context on system.

It seems we’re now in a world where engineers are responsible for creating a good environment where an agent is able to gain context on the architecture and validate its work via tests (e2e, unit, smoke, etc). Then it can get into its own feedback loop and find the correct solution on its own much faster.

[AlecSchueler]

> It seems we’re now in a world where engineers are responsible for creating a good environment where an agent is able to gain context on the architecture and validate its work via tests

Part of me feels like we could have increased both velocity and comprehension a great amount twenty years ago already if we'd only had the same considerations for our fellow developers.

[jonator]

Fully agree. Perhaps I should have clarified that it’s primarily for agents now, not just engineers.