Team Lead & Developer Resources

Many of these are aimed specifically at team leads, but there are more general articles as well. If you're a lead, you will probably also want to have a look at the Engineering Manager resources, particularly if you're leading a large team or multiple teams.

Code reviews

Culture

Documentation, Communications and Status

  • Want to be happier and more successful? Write about yourself every week.
  • Making Engineering Team Communication Clearer, Faster, Better - Patterns for design documents & design reviews "Most engineering teams rely on design documents to describe, scope, and approve projects or features. Those aren’t new in and of themselves (they're just the foundation of what we'll talk about here). Kicking off a project without one would be like a hiker heading into the forest without a map. Engineering teams don’t have that kind of time."
  • What nobody tells you about documentation - "There is a secret that needs to be understood in order to write good software documentation: there isn’t one thing called documentation, there are four. They are: tutorials, how-to guides, explanation and technical reference. They represent four different purposes or functions, and require four different approaches to their creation. Understanding the implications of this will help improve most software documentation - often immensely." Blog post from Divio.

Ethics

Mentoring

OKRs

Pair Programming

Planning and Stories

Self-organizing Teams

  • Designing Autonomous Teams and Services - "Modern, high-performing organizations employ continuous discovery and delivery to develop better products faster than their competitors. They are constantly running experiments to discover innovative new ways to solve customer problems, and they build high-speed engineering capabilities to deliver value every day, creating ultra-short customer feedback cycles."
  • Habits of High-Functioning Teams

Technical Debt

Technical Leadership

Testing

When Things Go Wrong

  • The Conjoined Triangles of Senior-Level Development - "The simplest explanation of seniority across companies is this: How much direction will this person need, and how much will they be able to provide to others?"
  • On Being A Principal Engineer - "I also realized that while I am still an individual contributor, the principal engineer role carries enough cross-organization work, and enough people skills, that it is much closer to management than it may seem without engineers reporting directly to me."
  • Cognitive Biases in Programming - As developers, we’re familiar with the various problems that interfere with our productivity. But often we overlook the broad picture. Some subtle, some huge, some you can do something about, and some you just, well, can’t. These all combine to form a sort of internal feedback loop that can lead to lost hours of productivity, bugs, and just all-around frustration. If we can minimize the impact of one or two of these, we can break the cycle and neutralize the rest.
  • The Effective Tech Lead is a 100x Engineer - The Webflow Tech Lead Guide
  • Techie to tech lead: My five biggest mistakes - Some advice from a current Head of Technology at ThoughtWorks: "As a young, ambitious developer with a strong sense of my own talent, I was eager to become a tech lead, and it took less than four years for me to achieve this goal. But over the next two years, the experience and reality of leading a team put me off leadership completely. For several years after, I retreated into the security of the technology, shunning any opportunity to take on more responsibility. Over time, I gained an understanding of the root causes of my mistakes and eventually regained the confidence to accept new leadership opportunities and grow as a leader, and with the right support over the last two years, I've grown as a Head of Technology inside ThoughtWorks. As I have coached and mentored other leads, I’ve learned that some of my mistakes weren't unique to me but are common among technologists who move into leadership."
  • How to Grow as an Engineer (Working Remotely) - "I have over 20 years of experience as an engineer or engineering manager. I’ve spent the last seven years working for The New York Times, and have been remote for the past three years. How do I keep myself constantly learning and growing, both personally and professionally, while at the same employer, especially now that I’m a remote worker?"
  • Being Glue - How to handle it if you move into a less-coding but still-technical "connector" role
  • DACI Playbook]]from Atlassian
  • Software Development is more like a professional competition than building a house]] - Metaphorical exploration from Christopher Drappier

results matching ""

    No results matching ""