In the pre-agentic era my view was that the main purpose of the code was communication between team members. This doesn't really change for me in the agentic era, at least not yet. So I prefer the code to be clear and understandable, and that's not really that hard to achieve by following the ideas and principles of modularity, high cohesion, loose coupling, separation of concerns, good naming, right amount of engineering. The problem in my view was that most folks went between two extremes. One were pre-agentic sloppers, and others were overcomplicating the code design for the sake of the design (often appealing to the authority of self-proclaimed relatives & such). The latter camp definitely made the code more complicated than needed. But I disagree with the premise that a well-organized code has a cost. Code is information, and organizing that information is to me an essential part of my job.