Things I Think About at 2am

• How can we design for future scalability without adding unnecessary complexity in the short term?
• What is the ideal team structure so everyone is productive yet teams don't step on each others work?
• How can we build infrastructure to prevent yesterday's production defect from recurring?
• Which stakeholders need to be involved to ensure the best possible decision?
• How do we migrate the code to meet modern standards without massively expensive rewrites?
• What off the shelf component might best be leveraged to simplify implementation of a new feature?
• Where can we find the best people to hire?

Things you Might Not Know About Me

• I first used a computer at the Science Museum in London. Ever since then I have been fascinated with them.
• The first program I wrote was a mathematical model of a roulette system I read about in the book Thirteen Against the Bank.
• My first paid programming project was a numerical analysis of heat flow through the skin of reentry vehicles. This was written in fortran 4 and ran on an IBM Mainframe
• I once left a photograph of myself as an easter egg in a web application delivered to a major software company. The photograph was still there years later - even as the application had been refactored beyond recognition.
• I am listed in the acknowledgments for Jessica Burdman's book Collaborative Web Development: Strategies and Best Practices for Web Teams. She chose a project I worked on as a case study in the book.