4 ms·
Simple is almost always Correct. Conversely, complex is almost always incorrect.
by jamiesonbecker 13y ago
Simple is almost always Correct.
Conversely, complex is almost always incorrect.
- mercurial 13y ago"Simple enough is almost always correct". "Too simple for the problem domain" is almost always a synonym for "build a heap of absolutely terrible and verbose pile of complexity on top of the 'simple' system". See also sysvinit.
- kelnos 13y agoStrongly disagree. Often complexity in your implementation is necessary to present a simple interface to your user.
- eikenberry 13y agoThe primary user of your implementation is the next developer to maintain it.
- kelnos 13y agoThe user of a piece of software is more important than its current or future maintainers.
- rschmitty 13y agoYes but current or future users want reliability, features, and speed. If you care about your users in the long term you should care about the project's maintainers.
- kelnos 13y agoI suggested a relative ordering of importance; nowhere did I imply that one was important and the other was not.
- eikenberry 13y agoThinking like this is why we have so much crappy software out there.
- bitwize 13y agoTo quote Ryan Dahl: The only thing that matters in software is the experience of the user. How many more times must it be said? How many more times must Apple win -- and win big -- before open source nerds get the message?