I've just recently had to switch back to doing development on a Windows box, after a couple years of using a Mac (and still using a Mac for my personal work).
There are many things that frustrate me. In particular, the Console (cmd.exe), even with with Cygwin installed, is horrible. In search of a better terminal, I came across Console2 http://bit.ly/bKPvqq .
After reading this article in Harvard Business Review (http://hbr.org/2010/01/success-gets-into-your-head-and-changes-it/ar/1) and this one in Wired (http://www.wired.com/magazine/2009/12/fail_accept_defeat/all/1) I was once again reminded of all the smart people who have advocated doing retrospectives to improve team performance.
This blog by Ty Kiisel sums it up nicely http://blogs.attask.com/blog/strategic-project-management/0/0/the-projec....
While in Port Clinton over Christmas break Quay got a chance to play piano with Grandma Akins
Many core concepts related to software development performance have been addressed while writing about speed of delivery. Hopefully, it is becoming clear that speed of delivery is a localized effect and can't be generalized to all teams for all products. This final entry on delivery speed addresses the responsibility that engineers and product managers have for identifying how to best choose an architecture that allows the team to optimize speed of delivery and make good decisions about when to evaluate architectural changes to prevent a prolonged degradation of delivery perform
Insomnia keeps me up at night. Thinking about what it takes to create good software; convincing people to create good software; and the feedback cycle necessary to ensure that the two sometimes divergent goals stay in parallel.
I'll be posting blogs describing software development and will also include some tutorials to help folks get through "Iteration Zero" on new technology.