7 Phrases I Use To Make Giving Feedback Easier For Myself
- Wes Kao tl;dr: “Having the right words can be the difference between doubting whether to speak up at all, or voicing your point of view confidently. With that, here are 7 phrases I often use when sharing feedback that makes it easier for me to speak openly and quickly, and encourages my recipient to take action.“featured in #608
Twenty Tiny Leadership Lessons
- Subbu Allamaraju tl;dr: “Most leadership learning is experiential. We observe, learn, and emulate from others, often subconsciously. Yet, the core of such learning starts shallow, leading to behavioral and decision-making mistakes, learned and uncorrected bad behaviors, and dysfunction. Some get better with experience and scope, but more often than not, we wing it, frequently repeating the same behaviors and mistakes for years.” Recognizing this, Subbu enrolled in the Psychology of Leadership at Penn State University. He shares the top twenty from those studies.featured in #608
Developers Don’t Need More Documentation
- Dennis Pilarinos tl;dr: Docs get written, but answers stay hard to find. The problem isn’t the docs themselves. It’s that the context developers need is scattered, outdated, or missing entirely. Why does this keep happening? And what’s the alternative?featured in #608
How To Get Better At Strategy?
- Will Larson tl;dr: Will covers: (1) Exploring strategy creation to find strategies you can learn from via public and private resources, and through creating learning communities. (2) How to diagnose the strategies you’ve found, to ensure you learn the right lessons from each one. (3) Policies that will help you find ways to perform and practice strategy within your organization, whether or not you have organizational authority. (4) Operational mechanisms to hold yourself accountable to developing a strategy practice. (5) My final benediction to you as a strategy practitioner who has finished reading this book.featured in #607
Mistakes You Shouldn’t Let Your Reports Make
- Bjorn Roche tl;dr: There are times when leader must head-off mistakes. Here are a few examples: (1) Starting a project that likely won’t ship, or won’t benefit the company. (2) Believing a pet project will get them outsized recognition. (3) Making a decision that will commit the company to something that isn’t a good long-term fit. (4) Over-emphasizing long-term or abstract benefits to the detriment of shipping. (5) Diving in too quickly to make changes to a system, resulting in unforeseen or unpleasant consequences for other teams.featured in #607
Innovations In Evaluating AI Agent Performance
tl;dr: Just like athletes need more than one drill to win a competition, AI agents require consistent training based on real-world performance metrics to excel in their role. At QA Wolf, we’ve developed weighted “gym scenarios” to simulate real-world challenges and track their progress over time. How does our AI use these metrics to continuously improve our accuracy? Visit our website to learn more.featured in #607
The Million-Dollar Problem Of Slow Microservices Testing
- Arjun Iyer tl;dr: When integration tests run after code merges, fixing failures becomes costly and time-consuming. Uber, Lyft, and Airbnb tackled this with an innovative approach to ephemeral environments that avoids infrastructure duplication, enabling pre-merge testing for every change. Discover how this "shift-left" strategy catches integration issues early and saves millions in engineering productivity.featured in #607
The Precise Language Of Good Management
tl;dr: “In the squishy realm of managing humans, the specific things you say have specific outcomes. Unfortunately, most managers are very bad at speaking precisely. Speaking precisely, especially about long-term, uncertain things, is not something many people do by nature. Let’s explore some common examples of imprecise language and how to fix them.”featured in #606
featured in #606
Why Documentation Fails Developers
- Dennis Pilarinos tl;dr: Developer documentation is a paradox. Teams spend hours writing it, yet it’s often outdated, incomplete, or hard to navigate. But the solution isn’t writing more or centralizing documentation—it’s surfacing the context where developers need it.featured in #606