3 ms·
Generally, it's much easier to add complexity than remove it once it has been added. > So when you throw this code at your developers, it means that you'll end
by acveilleux 10y ago
Generally, it's much easier to add complexity than remove it once it has been added.
> So when you throw this code at your developers, it means that you'll end up with hundreds or thousands of little methods all similar but all different.
If that's what happens with your developers, you need new developers or new management, clearly the ones you've hired are either incompetent or their management is forcing them to suck.
- gerbilly 10y ago> If that's what happens with your developers, you need new developers or new management I don't think so, it's just human nature and other pressures besides the purely technical ones: like the pressure to just get a task done, or to get the job done as easily as possible, and so on...[1] As programmers we tend to think the the biggest challenges are technical, but they aren't: the social problems are a way bigger factor. Also the problem I'm describing here applies to large low-complexity codebases, to be worked on by large teams. These are common in 'enterprise' settings, which is why I think design patterns have so much appeal there. [1] https://en.wikipedia.org/wiki/Tragedy_of_the_commons https://en.wikipedia.org/wiki/Tragedy_of_the_commons