3 ms·
Keep it simple, use boring tech, etc. We know. The whole issue is what is boring, what angle we wish to view simplicity/complexity from. These pretty much alway
by draw_down 6y ago
Keep it simple, use boring tech, etc. We know. The whole issue is what is boring, what angle we wish to view simplicity/complexity from. These pretty much always boil down to “what I like”. What I like is simple and boring, your stuff is shiny and overengineered.
- JKCalhoun 6y agoHe gave examples that would be more accurately described as "tried and true" not "your stuff" — the code that has been battle tested in the field for decades.
- civilized 6y agoIt's not hard to find things that virtually everyone agrees are complicating and shouldn't be used in a project unless they have clear benefits. Metaprogramming. Macros. Multiple inheritance. Multiple languages. The silver pants unicyclists know this too, they just lack impulse control.
- strulovich 6y agoI think this gets to the next level of the problem. Some people (usually earlier in their career) really get attracted to weird shiny stuff. But in reality, discussions I have about arguing for simplicity have two opposing sides both basing on tried and true technologies in their opinion. I find a good solution is to have reviewers and outsiders who can give feedback, and generally trust them when they recommend avoiding something. (But I have seen the cases where this exact approach would have killed a crazy idea that became a huge success story later on) Almost everyone wants simple. But simplicity is subjective. My simple can be a touch screen and yours can be buttons and we would both be correct.