57 ms·
The simplest code is an empty file. And yet, we live in a world with complex software. There are tradeoffs, but this article doesn't help you make them.
by hawkice 8y ago
The simplest code is an empty file. And yet, we live in a world with complex software. There are tradeoffs, but this article doesn't help you make them.
- tumdum_ 8y ago> this article doesn't help you make them Sure it does. It clearly states that sometimes new features or performance optimisations have to be sacrificed to keep the software simple.
- DannyB2 8y agoComplexity for new features or performance optimizations is simply a trade off. Sometimes one worth making. By adding a lot more complex code can I make this blitter 100 times faster? By using this more complex algorithm can I make a "simple" string search amazingly faster? As for features: Word has more features than Notepad. So why doesn't everyone use notepad?
- hawkice 8y agoThat's like saying, sometimes apples are so expensive you can't buy them. Perhaps surprising, if you haven't thought of it, but it is an obviously true statement about all tradeoffs. Sometimes you shouldn't make them. Still doesn't help you figure out when you should.
- tumdum_ 8y agoMaybe it’s obvious to you but at least in my experience lots of devs when confronted with feature request rarely consider if said feature should be implemented. Most of the time they only think how it could be implemented.
- styfle 8y ago> The simplest code is an empty file Reminds me of this: https://github.com/kelseyhightower/nocode https://github.com/kelseyhightower/nocode