5 Ways to Stay Productive as a Self-taught Developer

December 04, 2019

As a self-taught developer, it can be tempting for me to watch an episode (or two) of Bon Appétit instead of fixing that bug, starting that new project, or practicing that new skill on my evergreen list of things to learn.

There are definitely times I’ve chosen the YouTube video over my projects. But now that I’m three months into my self-taught developer journey and have gone through some trial and error, I’ve found the productivity methods that work for me.

These are five ways I stay productive:

1. Set metrics for success

Every quarter, I set learning goals along with metrics for each goal using OKR methodology. See my OKR explanation here. Knowing that I have ambitious yet reasonable goals keeps me motivated. And on the days I’m feeling unmotivated, this structured roadmap keeps me disciplined to stay on track.

2. Work in intervals

I like to work in 30 minute blocks with 5-10 minute breaks in between. This is also known as the pomodoro technique, a time management method.

3. Change in working environment

My usual working spot is home, so it’s nice to have a change of scenery. This usually means working from a cafe or the climbing gym if I’m between commute and my next meeting. I especially like working from cafes when I’m stuck in a rut because the light background noise paired with a warm latte helps get my creative juices flowing.

4. Social accountability

I tweet about projects and small learning goals to keep myself accountable. It’s a must that I finish a project since I’ve announced it to the people of the internet, right!? If I’m feeling really good about a project, I share it with my friends to get the obligatory, “It looks great!”. But I also use it as an opportunity to solicit feedback for improvement.

5. Project management

Even for solo projects, I enjoy using Trello to keep myself organized. See an example here. Writing out MVP and bonus user stories at the beginning of the project has allowed me to better scope out and estimate the time needed to complete a project. The satisfaction of moving a card from the “backlog” to “in progress” to “completed” also keeps me motivated. Most importantly, defining MVP user stories has helped me see the endpoint of the project, which has resulted in less unfinished projects.

If you’d like to share any tips on how you stay productive, I’d love to hear them in the comments!

Originally posted on dev.to.

Up Next