If you, like me tend to carry around or "cloud around" a single .emacs file so you end up with similar environments wherever you have an Emacs install, you know it's a little painful to ensure that you have the same set of basic packages installed on each one of your Emacs installations. As I had mentioned before I don't use that many third party packages so my Emacs configurations aren't that complicated, but I always prefer to have the computer remember things so I don't have to.
A common annoyance with Emacs when working on a code base that has duplicate file names is that the mode line tends to display the buffer names as "one.py:<1>", "one.py:<2>" etc etc. That doesn't help much with telling them apart and I find it confusing.
Interesting story how a development team at Facebook debugged a resource handling issue in their iOS app.
A couple of interesting articles about debugging. Debugging doesn't seem to get a lot of attention when people are taught about programming, I assume you're supposed to acquire this skill by osmosis, but it is actually one of those skills that should receive much greater attention because it's one of those that separates highly productive developers from, well, not so productive ones.
Putting the OpenSprinkler and Raspberry Pi together was easy, getting them to run showed my inexperience when it comes to playing with hardware. The overall install went pretty smoothly and the documentation is good and easy to follow so I'm not going to ramble on about it for very long, but just throw up some notes.