On: One cost engineers and product managers don't consider

[pedalpete]

Would anybody speculate that the popularity of MVC and agile development has exacerbated this issue?

I'm working for the first time on somebody elses code and with a group of develpers, and it seems like the answer to most problems is 'just add another model'. I stay away from that as much as I can, and try to make existing models fit new features and functions.

Maybe it's just my current workplace, but is this a more modern problem?

[jqjester → pedalpete]

I'd rather have two simple things than one complex thing.

In the codebases I've worked on, a lot of the complexity I see arose from people changing the meaning of existing code so they could 'reuse' it.

[krakensden → pedalpete]

if you aren't allowed to spend more than 1-2 days writing and testing any particular unit of work, agglomeration is the dominant strategy.