/Management

Technical Coherence

- Jack Danger tl;dr: “Software development slows down over time. I wrote a whole book to help leaders reverse this slowdown and the central point of the book is a process any engineering leader can apply. I call this process Technical Coherence and you can mostly achieve it in a single meeting with your leaders. You can implement it in your org gradually or all at once.”

featured in #547

Ad Hoc Infrastructure

- Kent Beck tl;dr: “My intention in this note is to reclaim the phrase ad hoc from those who use it as a pejorative, especially as applied to infrastructure. Instead, building infrastructure ad hoc is the safest, most efficient strategy. It carefully balances the risks inherent in creating infrastructure, stages investment, and realizes economies of scale.”

featured in #546

Technical Coherence

- Jack Danger tl;dr: “Software development slows down over time. I wrote a whole book to help leaders reverse this slowdown and the central point of the book is a process any engineering leader can apply. I call this process Technical Coherence and you can mostly achieve it in a single meeting with your leaders. You can implement it in your org gradually or all at once.”

featured in #546

Differing Values In A Team Are Costly

- Raphael Gaschignard tl;dr: “A team has a set of values, and members of those teams have values. If everyone is in perfect alignment, you might argue that there are blind spots. But if people are highly performant along those axes, then the blind spots almost don't matter. Meanwhile, if you have a team of 2 people, and they have a huge values gap, their job now becomes a tug-of-war, on top of the normal work of building things.”

featured in #546

Heartbeats: Keeping Strategies Alive

- James Stanier tl;dr: “The heartbeat is a communication that looks back at the strategy, recaps the key points, and then shows how it has been implemented in the time since the last heartbeat. It's a chance to show how the strategy is living and relevant, and that it's not just a document that was written once and then placed on the shelf.” James shares strategies for doing so. 

featured in #545

Demanding And Supportive

- Ravi Gupta tl;dr: “Most people think of demanding and supportive as opposite ends of a spectrum. You can either be tough or you can be nice. But the best leaders don’t choose. They are both highly demanding and highly supportive. They push you to new heights and they also have your back.”

featured in #545

The ROI Comparison Of Building SSO And SCIM vs. Using A Pre-built Solution

- Min Kim Kristopher Hughes tl;dr: For high-growth startups, time is the single most important resource. It’s so important that months of delay in shipping SSO and SCIM can result in a potential revenue loss of $7.95M compared to using a pre-built solution. The ROI difference is staggering too: 9% for a homegrown solution vs. 1,954% for a pre-built one. This article explains the methodologies used to calculate these numbers.

featured in #545

Engineering Team Meeting: Format & Topic Ideas

- Marc Gauthier tl;dr: “When I started managing the engineering department at my company, I wanted to have an interesting team meeting involving the entire team. My objective at the time was to set up a meeting that people would look forward to, going beyond simple team & company updates. It’s now been a few years since the first, and while not all presentations are a complete success, I’m pretty happy with the way it turned out.” Marc discusses the meeting format. 

featured in #545

Let Small Fires Burn

tl;dr: “Humans are bad at judging the absolute value of things. We can't estimate tasks, can't assess what's important, and we're poor predictors of impact. But we’re really good at taking two problems and saying "Yep that one's worse than the other one". You can take this insight and use it to create an ordered list of priorities. Go pair-wise through your fires, swap to put the bigger fire on top, and after n^2 iterations you'll have a stack ranked list of fires from biggest to smallest.”

featured in #545

Manager Antipatterns

- Ted Neward tl;dr: “There's a whole host of mistakes that companies often fall prey to with respect to those they have leading teams, and I thought it a good idea to collect them into one place, under the umbrella heading of "manager antipatterns”.”

featured in #545