Photo by Max Duzij
“The Productive Coder”? You must be one of those 10x programmers. Share your wisdom, o wise one!
Someone (maybe you) finding this site
Am I the “Productive Coder”? Hardly. I created this because I needed it.
Oh, so you suck?
You, as you reach for the mouse to leave the site
Sometimes.
Sometimes I’m very productive, but it can be hard to predict. Sometimes the code that was supposed to be hard to write flies off my fingertips. Sometimes the easy job drags on forever.
Maybe it’s been the same for you. Maybe, like me, you bought books like Getting Things Done by David Allen, or Tiny Habits by BJ Fogg. Reading the book, you thought “This is amazing! I’m going to be amazing!”
Maybe, like me, nothing much changed after reading the book.
Two Inescapable Facts About Productivity
You need to find tactics that work for you.
You need to do them.
My writing in The Productive Coder will focus on these two facts.
Find what works for you: It doesn’t matter if some author made massive productivity gains with one simple trick. What matters to you is whether you can discover tactics that can help and knowing when they will work.
You need to do them: This is where the perfect process can fall apart. You need to do it. There’s a corollary to this rule. You need to be aware of whether or not you’re using the tactic. I’ve certainly had times when I intended to do something like use a
timer, only to realize I’d forgotten to restart it. You’ve probably done the same.
How Can You Use “The Productive Coder”
The guide to get you started is here:
Don’t limit yourself to the tactics I suggest. Find inspiration in books and articles. Definitely try to come up with ideas of your own.
As you discover the tactics that work for you, be sure to let me know.
