3 ms·
20 years of experience here. My little contributions: 21. Do not mistake hype and popularity for quality. 22. The best code is no code, but configuration is w
by goodpoint 5y ago
20 years of experience here. My little contributions:
21. Do not mistake hype and popularity for quality.
22. The best code is no code, but configuration is worse than code. Maintaining 1000 lines of YAML is worse than 9000 lines of code.
23. The best code is no code, but replacing a script with a zoo of tools and libraries is often worse.
- marcosdumay 5y agoThe best code is no code; the second best code is high quality third party code; the third best code is your code; the worst code is low quality third party code, and that one is by a huge margin.
- goodpoint 5y agoNicely put. Yet I would add that your code is preferable to third party code if you can solve the same problem with 10x less SLOCs or complexity.
- marcosdumay 5y agoTo change a completely misunderstood citation into a new one that nobody will understand either: > Unnecessary flexibility is the source of all evil Just as with the original "premature", the word "unnecessary"is doing a lot of heavy lifting here, and there's no way to state that rule that saves people from thinking before applying. Some times those 10x SLOC are really important and will save you; most times it's just a 90% waste ratio multiplied over your previous one.
- dgb23 5y agoI think I somewhat disagree with 22. Not specifically in terms of YAML or what is categorized as configuration (basically anything?). I think a well designed data model is much more productive and simple than arbitrary code.