How to Unblock Yourself


Team-Driven Developer

A newsletter with tips and tools for building software as a team

You’re staring at your editor. The code should work, but you’ve been fighting an error for a full day. You can’t figure out the problem no matter what you try.

Or you’ve been staring at an empty file, wondering what code to write. You’ve got a vague Jira ticket, a lack of context, and a codebase that is difficult to understand.

You’re blocked.

Now, what do you do?

It’s tempting—easy, even—to ping someone hastily. You drop a question in Slack like “Anyone seen this error before?” and hope someone tosses you a lifeline.

Or it might be equally tempting to throw prompt after prompt at AI, hoping for a different result.

In this article, I want to describe some tools for overcoming obstacles in these situations. As you grow in your software engineering career, this skill becomes more and more important as you’re expected to work with increasing autonomy.

Let’s dive in.

Team-Building Exercise

When it comes to being blocked, great teams proactively (not reactively) help each other stay unblocked.

  • They swarm on toil to remove from their daily work
  • They share solutions to common problems—and then figure out how to remove them entirely
  • They participate in backlog refinement and planning since they know they will be the ones picking up that work soon
  • They anticipate confusion about scope, context, etc., as best as possible, and welcome questions patiently when needed

While unblocking yourself is a skill, helping the entire team stay unblocked is even more critical.

Don't take shortcuts on things like daily work, planning large efforts, or even how you align on decisions.

This week, be purposeful in how you work to keep others unblocked. Keep PRs to an appropriate size, spend time writing your stories and planning work, and be active in your team meetings.

Intentionality like this doesn't guarantee people never get blocked or need help, but I do guarantee they will get blocked more and for longer without it.


Here are some more resources from me to help you build better teams!​

  • 📕 Code Review Champion - My book on code reviews will help you become a world-class code reviewer. From giving kind feedback to navigating conflict, this book can help anyone wanting to sharpen their code review skills.
  • ❓​Questions for Devs - Building a team takes more than catching up about your weekend at standup. I've used these questions to build relationships with my team and push past the same old surface-level conversations.
  • ​📋 Pull Request Template - Maximize your efforts in pull requests by giving context right at the beginning of a new pull request. Copy and paste this template into your repo, and voilà!
  • 📊 ​Code Review Metrics - Start measuring how your team tracks against a few common code review metrics. This python script will pull your GitHub pull requests and generate a CSV you can slice-n-dice to get the data you want. It also has graphs! As this is an open-source project, your contributions and feedback would be great!

Other Creators I Recommend

Image for Looking for your next tech job?

Looking for your next tech job?

You're in the right spot. I'm Dr. Kyle Elliott, the founder and tech career coach behind CaffeinatedKyle.com, and I love giving away free resources that help to ensure your job search and career success.

Join 7,435+ fellow job seekers who have downloaded my free Job Search Launch Guide.

Image for The Mindful Dev

The Mindful Dev

Dagna is an Engineer turned Coach for ambitious professionals in Tech. She has transitioned from programming computers to reprogramming human minds. Her book Brain Refactor is a recognized Amazon bestseller, helping professionals optimize their internal programming to thrive in tech.

113 Cherry St #92768, Seattle, WA 98104
Unsubscribe · Preferences

Dan Goslen | The Team-Driven Developer

Learn the tips and tools for building software as a team! Every other week, I send a long-form article, a team-building exercise, and resources to help you build better software teams so you can build better software.

Read more from Dan Goslen | The Team-Driven Developer

Team-Driven Developer A newsletter with tips and tools for building software as a team We've recently started a group at Webflow to enhance our existing code review process.And it made me think of an older article I wrote all about the point of pull requests. In a nutshell, pull requests aren't the same as a code review, but they are a common channel to help code reviews run smoothly. I rewrote and added some parts of the article based on the discussions we were having as a group, and wanted...

Team-Driven Developer A newsletter with tips and tools for building software as a team If you’ve ever joined a new team, tackled a legacy codebase, or stepped into an unfamiliar domain, the feeling can be overwhelming. There’s too much to know—and not enough time to learn it all. That’s why I use a model I call traversing the knowledge graph. It helps me orient quickly, pull in the most relevant context, and start contributing with confidence. In this post, I’ll describe: How I think and...

Team-Driven Developer A newsletter with tips and tools for building software as a team Imagine reading a technical design document or RFC. As you read, you notice that the language in the document is a bit confusing. For example: Requests likely need to be authorized using standard HTTP auth mechanisms What does this “requirement” mean? Are we using “standard” Authorization headers with base 64 encoded usernames and passwords? I don’t see a mention of HTTPS. And I also don’t know what...