3 ms·
It's a question of framing. Nothing is ever over- or under-engineered. It's over- or under-engineered for a purpose. What that distinction recognizes is that i
by mumblemumble 5y ago
It's a question of framing. Nothing is ever over- or under-engineered. It's over- or under-engineered for a purpose.
What that distinction recognizes is that it's possible for something to have been well-engineered at one time, while still being over-engineered today. Header files in C and C++ are an example of this phenomenon. They solved a very real problem with technical constraints from 40, 50 years ago, both in terms of computers' capabilities and compiler technology, but, since those problems don't exist anymore, they function as over-engineering.
- selcuka 5y agoAgreed, but "nothing is ever over- or under-engineered" is a bit too bold. There is definitely over engineering just for the sake of over engineering, and under engineering caused by incompetency.
- blt 5y agoWhat is the less-engineered alternative to header files?
- mumblemumble 5y agoSymbolic imports. Basically, the way every programming language newer than C++ or Objective-C does it.