http://chrismm.com/blog/how-terrible-code-gets-written-by-perfectly-sane-people/?2
https://news.ycombinator.com/item?id=13679499
"The law of averages is a layman's term for a belief that the statistical distribution of outcomes among members of a small sample must reflect the distribution of outcomes across the population as a whole."
"A good way to know if a metric is useful or not, is to try to understand what personal values it outlines. Concentrate on metrics that advertise good attention to details, good communication skills and good attitude, especially if they require great effort to cheat."
blog-post-how-terrible-code-written#tdd-defect-rate1"This is where proven practices step in, and there are a few of them. Test-driven development has been shown to reduce defect rates 40% to 90%, with an increase in development time in the 15%-35% range. Code reviews have also been shown to decrease defect rates, in some cases up to 80% over manual testing." blog-post-how-terrible-code-written#tdd-defect-rate1
blog-post-how-terrible-code-written#hacker-news-comment-easy-remove-code1 2By default, good code tends to be modular and easy to replace, while bad code is excessively coupled and hard to get rid of. So bad code has a disproportionate impact on long-lived codebases. I wonder if one way around this is to force modularity, even when it's unnatural. Functional programming seems to be one way of doing this, microservices are another. A related principle would be not to take DRY too seriously, favoring decoupling over deduplication. blog-post-how-terrible-code-written#hacker-news-comment-easy-remove-code1 2B
References blog-post-exploding-software-engineering-myths book-making-software-what-really-works