Without over-training on this one incident, and without guidance on how to get from here to there (I'm still working on that): 1. Don't get suckered by interfa

Without over-training on this one incident, and without guidance on how to get from here to there (I'm still working on that): 1. Don't get suckered by interfaces, share code. If you create code for others to share ("libraries"), stop trying to hide its workings. 2. You don't have to learn how everything works before you do anything. But you should expect to learn about internals proportional to the time you spend on a subsystem. Current software is too "lumpy" -- it requires days or months of effort before yielding large rewards. The first hour of investigation should yield an hour's reward. 3. "Production" is not a real construct. There will always be things that break so gradually that you won't notice until they've gone through all your processes. Give up on up-front prevention, focus instead on practicing online forensics. And that starts with building up experience on your dependencies. More elaboration: http://akkartik.name/post/libraries2 http://akkartik.name/post/libraries2 My attempt at a solution: http://akkartik.name/about http://akkartik.name/about My motto: reward curiosity.