Being entirely forward-focused isn’t actually the best approach to running software teams. Here’s why your codebase history is a valuable leadership tool.
“Underpromise, overdeliver” has become something of a mantra when it comes to delighting customers. But when we adopt this mindset with our colleagues, it becomes something else entirely.
Engineering organizations have focused exclusively on the work product (what has been built) while ignoring the work process (how we did building it) – until now.
The myth of “healthy tension,” and a more holistic approach to handling the conflict that will inevitably arise in your team.
We often fail to look beyond our intuitive notions of ‘scaling’. So before you start hiring more people, consider these common ‘traps’.
After working with hundreds of customers and analyzing over 40 million commits, here are the top 3 misconceptions engineering leaders have about Code Churn.
GitPrime’s CEO, Travis Kimmel, on Measuring Software Engineering Productivity — with SE-Radio, the podcast for professional software developers.
Everything you need to know about the experience of self-forming teams, and a workbook to help you get started.
The characteristics that define a successful remote hire, and how teams at GitHub effective work together.
We equate ‘speed’ to being busy, frantic meetings, and the flurry at the end of each sprint. But real ‘speed’ looks far different.
Over the last couple decades, our industry has seen a lot of changes in how we run engineering teams. Here’s a brief overview, and a look at what’s next.
Lara Hogan has dedicated her career to growing leadership in tech. Here’s what she taught us about honing the craft of management.
Get Engineering Impact: the weekly newsletter for managers of software teams
Keep current with trends in engineering leadership, productivity, culture, and scaling development teams.