30-60 Days In A New Leadership Role: Run Experiments For Change
- Lara Hogan tl;dr: "We’re intentionally limiting this process to two experiments because tons of change at once will be scary and confusing for folks. We’re also going to limit the experiment timeline to 2-3 weeks; the goal is to be able to gather data at the end of your first 60 days in your new leadership role." After crafting experiments, develop your communication plan, implement your experiments and prepare to share the results.featured in #385
How We Found Our Ideal Customer Profile
- James Hawkins tl;dr: "Creating an Ideal Customer Profile is one of the most important things we've ever done." James shows how this is reflected in the companies revenue. It enabled the company to make important decisions - they were better placed to describe what the company does, what the site looks and feels like, pricing model, and more. James also describes how the company approached creating this profile.featured in #385
A Framework For Prioritizing Tech Debt
- Max Countryman tl;dr: "Now with a complete list of your tech debt as it stands go through each and answer the following questions: (1) If we choose to do nothing, will this issue become worse, remain the same, or improve? (2) If it'll become worse, how quickly will it degrade? (3) If it remains the same, how much disruption is it causing today? (4) If it'll improve, at what point will it improve to the degree it's no longer an obstruction?"featured in #384
The Ultimate Guide To Software Architecture Documentation
- Patrick Roos tl;dr: "This guide shows you how to write, structure, visualize and manage software architecture documentation in a lean way using appropriate documentation tools."featured in #384
Refactor Your Code - Don’t Be Like Southwest Airlines
- Shanea Leven tl;dr: Devs don’t have a way to communicate the complexity hidden in their code to business leaders — they lack code visibility tools. As a result, refactors aren’t prioritized until you have a Southwest-sized crisis. Here’s 9 tips to avoid being southwest.featured in #384
We Invested 10% To Pay Back Tech Debt; Here's What Happened
- Alex Ewerlöf tl;dr: Alex discusses how "Tech Debt Friday" started at his org, what was learned and how it's executed: (1) We spend 10% of our time to deal with tech debt. (2) The first rule is not to create debt in the first place. (3) The PR that creates tech debt should come paired with the issue to deal with it. And more.featured in #383
featured in #383
Resilience And Waste In Software Teams
- Jessica Kerr tl;dr: Jessica explains resiliency in the context of the Southwest Airlines software failure. "When software is brittle, it falls over in production, and that falls to people to fix. While software can be robust to anticipated conditions, only people handle unexpected events. When software can’t even handle stuff that happens all the time, then people suffer the strain."featured in #383
Meetings For An Effective Eng Organization
- Will Larson tl;dr: "I’d like to recommend 6 core meetings that I recommend every organization start with, and that I’ve found can go a surprisingly long way. These six are split across three operational meetings, two developmental meetings and finally a monthly engineering Q&A to learn what the organization is really thinking about." Will discusses each in depth.featured in #382
What Big Tech Layoffs Suggest For The Industry
- Gergely Orosz tl;dr: Gergely discusses rapid shifts in the engineering job market. "It’s certain we’ll see a correction of 2021-22’s hiring frenzy and it’s a given that Big Tech will hire much less this year than in 2022, while the question remains whether other large tech companies will follow suit and announce layoffs in the coming months."featured in #382