I'm really struggling to see how to make architectural decisions with an agent. It's great when you're at a total loss for ideas, but when you already have some of the pieces it ultimately wants to drive all of the thinking and takes over. Then it just feels like you're deferring your experienced judgement. I've seen colleagues lose the ability to reason any more without asking the agent to do it for them, because they inherently don't see the point if the agent is going to end up doing the whole piece (and probably auditing/overruling anything they came up with on their own).
Why would you care about architecture? It was an issue when humans were writing code so architecture mattered in the sense that you needed a sweet spot between current requirements and future extensions.
The agent can rewrite half your codebase in one day, so architecture stops mattering for the most part.
trwhite · · focus · HN ↗
NotGMan · · focus · HN ↗
The agent can rewrite half your codebase in one day, so architecture stops mattering for the most part.
jandrewrogers · · focus · HN ↗
Some apps don't care about scalability and performance but many do. Ignoring architecture all but guarantees inefficient, wasteful software.