Always be testing 5 reasons to write tests for your code, including this little gem:
This task of facing yourself is one of the most brutal, but also most powerful, aspects of software development. Interview your code, and if you wouldn’t hire it after the interview, change it.
Mythical man month Exploding Software-Engineering Myths: comparative research on how code coverage, assertions, team structure and working remotely affects software development:
“To some degree, The Mythical Man Month formed the foundation of a lot of the work we did,” Nagappan says. “But we also studied other existing assumptions in software engineering. They can be good or bad, because people make decisions based on these assumptions. Our primary goal was to substantiate some of these beliefs in a Microsoft context, so managers can make decisions based on data rather than gut feel or subjective experience.”
Pave the way Rebecca Murphey presenting at JSConf2011 about the future of JavaScript.
No half-ass Kyle Neath on Relentless quality:
The caveat here is that you can’t half-ass quality. Dedication to “semi-quality” isn’t dedication at all. High-end design coupled with mediocre engineering can only produce a mediocre result.
Decisively undecided Do You Suffer From Decision Fatigue? The answer is “yes”, and this is one article you must decide to read. It relates to so much of what we develop and how we go about the process.
QotD @FreddyAmazin:
Yawning is your body’s way of saying 20% of battery remaining.