profile

Dan Goslen | The Team-Driven Developer

Writing Software and Gardening

Published over 1 year ago • 2 min read

Team-Driven Developer

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

I'm not much of a gardener, but my wife is all about it.
​
I've learned much from her (and Monty Don) about cultivating a successful garden over the years.

It's so much more than "make sure to water your plants."
​
It requires attention to the seasons, your sunlight, and your soil. It requires procuring the right plans for the garden you want, tending to weeds, and knowing when it's time to try something different.
​
All of these are similar to what we need to do in software to create a healthy software team and a healthy software system.
​
Today, I'm sharing how writing software is a lot like gardening and how a perspective of "tending to our software" often gets missed when we focus on just putting plants in the ground.

Team-Building Exercise

This week's focus is all about weeds. What weeds are in your code that you overlook over and over? Can you spot any weeds that will eventually strangle and choke out your "garden?"
​
You likely already have examples in your head of code you want to change. Code that every time you encounter, it makes things just a bit too hard. That is exactly the code we are talking about.
​
The question is this: can we prioritize any of these weeds in the coming weeks or iterations for our team?
​
A great way I've found to get items like this prioritized is to point to on-call time, incident counts, or upcoming product work that the team feels will be impacted positively by an investment in removing some of these weeds.

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 Building Custom SaaS Web Apps

Building Custom SaaS Web Apps

by Thomas McGee

I’m a web developer by trade, but I’m a creator at heart. As such, I constantly find myself making, designing, and coding new things to make life easier for creators of all kinds. Whether it be Radarist for managing your projects and tasks or Startboard for easily organizing your web bookmarks—I’m here to make it easier for anyone to earn online.

​

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

​

​

Dan Goslen | The Team-Driven Developer

Helping software engineers build better teams

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...

about 2 months ago • 3 min read

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...

2 months ago • 2 min read

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...

2 months ago • 2 min read