2 ms·
After all, we all are looking for technical challenges and want to implement interesting projects. In my experience everyone does, but the difference between t
by userbinator 8y ago
After all, we all are looking for technical challenges and want to implement interesting projects.
In my experience everyone does, but the difference between the complexity-worshippers and (for lack of a better term) simplicity-worshippers is that the former like to take a simple problem and blow it up with complexity, while the latter like to take a complex problem and make it simple. In other words, some people like the challenge of making things more complex, while others like the challenge of making things simpler.
To make a concrete example, complexity-worship would be something like using half a dozen different new web frameworks/languages/libraries to set up a personal blog, while simplicity-worship would be more like an H.264 encoder in a single file[1] or a self-compiling C-subset JIT[2].
One thing that seems somewhat obvious about the complexity-simplicity divide, and which could also explain the prevalance of complexity-worship, is that it is relatively speaking much easier to generate complexity than to reduce it, and unfortunately it seems the majority of developers just don't have the skill to reduce complexity. It's easy to glue a bunch of existing code together without really understanding how it all works; it's much harder to take a spec that dozens of experts have worked on for many years, and condense it into a concise implementation.
[1] https://news.ycombinator.com/item?id=18045494 https://news.ycombinator.com/item?id=18045494
[2] https://news.ycombinator.com/item?id=8558822 https://news.ycombinator.com/item?id=8558822