Re:One cost engineers and product managers don't consider
by jqjester on Friday June 21, 2013 @10:13AM
(#5918094)
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.
Re:One cost engineers and product managers don't consider
by krakensden on Friday June 21, 2013 @02:46AM
(#5916888)
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.
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?