3 ms·
> it implies that it's all zero sum and there's nothing that's ever unconditionally better or worse than anything else Not necessarily - to start with, a good
by placebo 8y ago
> it implies that it's all zero sum and there's nothing that's ever unconditionally better or worse than anything else
Not necessarily - to start with, a good trade-off is unconditionally better than a bad trade-off.
Also, progress brings with it increasing complexity. Recognizing the best path includes assessing many more parameters and is far more difficult than deciding whether to use a hammer or a rock to nail things. The puzzling nature of many people to over-complicate things instead of simplifying them makes the challenge even more difficult.
By the way, the closest thing I've ever found to a silver bullet in software development (and basically any endeavor) is "Keep it simple". While this is a cliche already, it is still too often overlooked. I think this is because it isn't related to the ability to be a master at manipulating code and logic, but the ability to focus on what's really important - to know how to discard the trendy for the practical, the adventurous methods to the focused and solid - basically passionately applying occam's razor on every abstraction layer. If this was more common, I think articles like "You are not Google" would be less common.
- mcguire 8y agoEver wonder how the Go team seems to get stuff done more efficiently than other groups? It's not Go, it's that they simplify (perhaps oversimplify).
- tracker1 8y ago> Not necessarily - to start with, a good trade-off is unconditionally better than a bad trade-off. Are you better off with a simple dokku server, or a k8s cluster? There's lots of good/bad on both sides... it really depends on your needs. You could use one locally or through dev layers and another for production.