3 ms·
Overengineering addiction. And often times it is hard to debate against someone "smart" wanting to introduce overengineered approaches. After all we are all sol
by Traubenfuchs 6y ago
Overengineering addiction. And often times it is hard to debate against someone "smart" wanting to introduce overengineered approaches. After all we are all solving hard problems and if the solution is super simple that would mean the problems we solve aren't hard enough to require the more complex solution...
- reallydontask 6y ago> Overengineering addiction. I think that is quite a good description of a common problem in software development these days. Needless to say that I have been guilty of indulging in it
- pythonaut_16 6y agoIt's probably not just a "these days" problem though. Thinking through my own experience and various anecdotes it seems like fighting over-engineering and complexity are staples of software development. Consider also that sometimes complexity/engineering really is warranted; either by the domain or by the tooling. In other words, avoiding complexity-domain mismatch isn't just a "these days" problem, it's a constant consideration in software development.
- berkes 6y agoThe difference is that "git flow" is there, documented, often already familiar with engineers. As opposed to something, however simple, that you design yourself. I don't think the term "overengineering" applies when you take an industry practice off the shelf. If anything is overengineered, it would be the simple solution that you "engineer" in house.