1. Follow your heart 2. Never volunteer for meetings, because then you become "The Guy" 7. If all else fails, ask your neighbor 9. If it's final, then it should be final 13. Decision trees 16. Always favor something that saves you 45 seconds 22. Assertions should assert on something 52. Monkey patching is for the zookeeper 72. Always try to work in a place where there are palm trees 82. Kernel panic is rarely good 86. If you ever see a cool test, run! 94. It's all slashes these days 97. Agile doesn't work if you just hear things 186. Always use an attached keyboard 763. We were talking about splitting purchase orders, they were talking about revision history, now they're talking about splitting purchase orders with revision history, and that's why agile works!All the best, Michael! This advice will carry you far.
Tuesday, November 5, 2013
The Rules of Software Development
Last year I was working at a large enterprise. Over the summer we had an intern join us, who I couldn't help but show the ropes. We managed to cover several rules of software development in just a few months. After the internship wrapped up, he was nice enough to forward the notes he took while on our team: