Photo by Jon Tyson
Welcome.
This is where to get started improving your productivity in writing software. It’s the first of four pages explaining how and why this method works.
Start Here (this page)
Why? (coming soon)
What is It?
You can think of the Productive Coder Method as just these two statements:
You need to find what works for you. (Development.)
You need to do it. (Operations.)
It really isn’t important what worked for the author of the latest productivity book. What is important is what helps YOU be more productive NOW. I can’t give you answers beyond universal things like “get enough sleep”, but I can give you the process to figure out what will make you more productive. This is sort of like developing software. First, you need to understand the requirements and the approach to solve the problem.
Once you discover the techniques to become more productive comes the hard part: you need to use them. Think of this like ongoing operations. You need to keep on top of your running system, monitor, fix bugs, and perform maintenance.
Think of this as a simplified DevOps loop. At any one time, you’re either finding and improving your tactics or making sure they are being used the right way.
This is simpler than many of the DevOps or agile process loops you’ve seen. This simplicity is necessary because a simple system will take less of your time and will be easier to jump back in if you ever get off track. Also, it’s good to keep in mind that this is a never-ending process of improvement.
