Software Lead Weekly
Day 25 after signup
SWLW #728: Struggle together, Extensible software in the age of LLMs, and more.
Weekly articles & videos about people, culture and leadership: everything you need to design the org that makes the product.
Why it works
- Group recommendations into clear editorial sections so readers can scan topics and choose what interests them.
- Add a short point of view or a practical question beside each link to give the roundup a useful editorial perspective.
- Keep article actions consistent, such as offering the same save and share options throughout the issue.
How it is built
- Newsletter introduction
- Featured article commentary
- Sponsored product placement
- Culture article roundup
Email copy
A weekly newsletter by Oren Ellenbogen with the best content I found around people, culture and leadership in tech. You can also read this issue online and recommend this newsletter to your teammates for a great discussion. In a world where it's hard to keep up with so much content, I hope my curation helps you find high-signal content worth reading slowly and deeply. Under "Culture," you'll find content worth reading and sharing with others; you'll need others' help to pull it off. Under "Peopleware," you'll find content that can help you approach situations differently with new perspectives and frameworks. This Week's Favorite Struggle Together 4 minutes read. Worth stealing Addy Osmani's checklist and running it on your next non-trivial agent task: write down your hypothesis before asking, ask what would have to be true for this to be wrong, and have a second model argue the opposite side. Then read the command the agent ran and its output before you read its summary. It's a cheap way to teach your team what good verification looks like. Which of these could you make a default in your team's workflow this week? Read it later via Instapaper. Share it via Twitter or email. Product [sponsored] DX: Engineering intelligence for the AI era Measure and improve software health, R&D productivity, and AI-human collaboration for a truly AI-native SDLC. Track AI-generated code by commit, PR, team, agent, and repo to understand AI's real impact on productivity. Promote your product on SWLW and reach over 30,000 software leaders Culture This Is Exactly How I Feel Prompting My Agents 1 minute read. My humble effort to help you start the weekend with a smile. Read it later via Instapaper. Share it via Twitter or email. Open Source, Closed Contribution 8 minutes read. I like the idea that for the shared cores that survive, the code is no longer the product. Avishai Ish-Shalom argues the verifiable spec is, since it's the one check not correlated with any model's blind spots (SQLite's proprietary TH3 test suite is the example). If you build products with AI, how much of your investment goes into specs and tests versus the code agents write? Read it later via Instapaper. Share it via Twitter or email. ElevenLabs CEO and Former Palantir Deployment Strategist Gives One of the Best Explanations of What an FDE Is 3 minutes read. "In our case, FDEs are part of the product team. They are not part of the go-to-market team. They are deeply embedded in understanding what the roadmap of the product is." -- Mati Staniszewski (ElevenLabs CEO) puts it well. I agree, and the org chart matters here: an FDE reporting into sales will optimize for the deal, while one reporting into product optimizes for what the next hundred customers need. Read it later via Instapaper. Share it via Twitter or email. Extensible Software in the Age of LLMs 19 minutes read. Worth reading Jeremy Morrell's post as a checklist as your team builds anything that runs user or agent code. The five properties (cheap to run, fast cold starts, control over limits, solid isolation, safe actions) apply equally to extension platforms and agent sandboxes, and the survey of options (interpreters, V8 isolates, microVMs, WASM) helps you pick a starting point. Skim the Salesforce section first: it shows this has worked at scale since 2007. Read it later via Instapaper. Share it via Twitter or email. Peopleware Why Books Don't Work 17 minutes read. Great take by Andy Matuschak on why explanatory books mostly fail: the medium quietly assumes that people absorb knowledge by reading sentences. Swap "book" for "onboarding doc," "architecture RFC," or "engineering handbook," and the observation stays the same. What do you do in your team today to check that the idea landed, beyond sharing the document? I'm a huge fan of Andy Matuschak and took a lot of inspiration from how he structured his blog and launched Quantum Country (look it up!). Read it later via Instapape