How to be productive in two steps: 1. Use the right tool for the job - pen and paper when the idea is new in order to nail it down, then code later once all th

How to be productive in two steps: 1. Use the right tool for the job - pen and paper when the idea is new in order to nail it down, then code later once all the obvious pitfalls have been ironed out on paper first. It's amazing how going through a few use cases can drastically speed up development time instead of just diving straight in. 2. Think about maintenance - write clean code, keep it simple, and write tests (or at least write testable code). This article seems to suggest that you should work all day, consider toilet breaks as non-productive, and skip over exercise if you don't get your work done. A great plan if you want to work yourself into an early grave.