Tech Leadership Weekly, Issue 10 — Technical Debt, Guidance, and Gratitude
A weekly dose of management, process, and leadership.
First Round Review
Shims, Jigs and Other Woodworking Concepts to Conquer Technical Debt
Technical debt is a natural part of the software development cycle, and smart teams are constantly managing it. Dialog and conversation, before any code has been written, aligns the team to the approach. Pair programming and consistent code reviews are important as well. Modular code limits the impact of technical debt and simplifies the process of debt burn down. When a project accumulates too much technical debt, creating a rating system, including security concerns, prevalence, and the frequency of contact, can help a team prioritize which debt to focus on.
Reading Time: 8 minutes
Managing with Martians
When people come to you with a problem, often, our first reaction is to provide a solution. There are times when this is the right decision. More often, a better approach, is to provide a framework, some guidance for the desired direction, and let the individual choose their own path forward. You remove yourself as a micro manager, and allow the individual a learning opportunity.
Reading Time: 6 minutes
Ruining Habit #1: Ineffective managers don’t express gratitude
It’s important for the people on your team to know they are valued and appreciated. It can be hard to know when or how to say thank you. A thanks can come in the form of a note, an email, or part of a one on one. Showing gratitude is an valuable motivator. It’s important to show appreciation for those you appreciate.
Reading Time: 4 minutes
This content originally appeared in the Tech Leadership Weekly Newsletter. Signup for a weekly dose of management, process, and leadership delivered to your inbox every Wednesday at Tech Leadership Weekly.