How To Add An Onboarding Flow For Your Application
- Roy Anger tl;dr: Leverage Clerk’s customizable session tokens, publicMetadata and Next’s Middleware to create a robust onboarding experience within a few lines of code.featured in #535
The Biggest-Ever Global Outage: Lessons For Software Engineers
- Gergely Orosz tl;dr: “Cybersecurity vendor CrowdStrike shipped a routine rule definition change to all customers, and chaos followed as 8.5M machines crashed, worldwide. There are plenty of learnings for developers.”featured in #535
Trust As A Bottleneck To Growing Teams Quickly
- Ben Kuhn tl;dr: “Trust is what lets collaboration scale.” Ben shares symptoms he’s noticed that can indicate a buildup of trust deficits in companies: (1) Too many decisions needing to be escalated. (2) Too many decisions requiring deep involvement from many stakeholders. (3) People having lots of FUD about whether projects they’re not involved in are on track. (4) Leaders frequently needing to do “deep dives” on individual topics. (5) Leaders needing to spending most of their time. Additionally, Ben shares tactics to invest more effort in trusting others.featured in #534
Top 18 Products Launched With Speech AI
- Jesse Sumrak tl;dr: Whether you're a developer, founder, or product innovator, these fast-growing products are shaping the Speech AI space and demonstrating the endless possibilities unlocked by this technology.featured in #534
Where More Effective Product Teams Spend More (and Less) Time
- John Cutler tl;dr: “When trying to understand where a team or company is at, one of the first things I do is talk to people about how they spend their time and energy. Words like empowered, feature factory, and outcome-oriented are squishy and can mean a million things. Behaviors don't lie. There are only so many hours in a week, and we have finite energy to do thoughtful work.” John shares where teams that are further along their product journey spend time.featured in #534
Story Points Are Pointless, Measure Queues
- Barry Jones tl;dr: “Measured Queues address short term and long term estimation issues, handle scope changes naturally and provide a much more valuable exercise to larger teams while removing uncertainty from the team's initial plans. Measured Queues also provide a leading indicator of problems 20 times faster than Velocity or Cycle Time related metrics.”featured in #534
Developing Domain Expertise: Get Your Hands Dirty
- Will Larson tl;dr: “Some particularly useful mechanism for senior leaders to develop domain expertise are:” (1) Reviewing product analytics on a recurring basis. (2) Shadow customer support. (3) Assign named executive sponsors for key customers. (4) Directly use or integrate with the product. (5) Make an executive offsite ritual around using the product. (6) Use executive initiatives as an opportunity to dig deep into particular areas of the business. (7) Use a textbook or course driven approach.featured in #533
The Developer's Guide To RBAC: Part I
tl;dr: As SaaS products scale, supporting authorization becomes critical, requiring solutions like fine-grained access control (FGA) to meet complex enterprise needs. This guide covers the fundamentals of role-based access control (RBAC) and its limitations, trade-offs to consider when transitioning to FGA, and implementation details from companies like Figma and Carta that built these systems in-housefeatured in #533
Story Points Are Pointless, Measure Queues
- Barry Jones tl;dr: “Measured Queues address short term and long term estimation issues, handle scope changes naturally and provide a much more valuable exercise to larger teams while removing uncertainty from the team's initial plans. Measured Queues also provide a leading indicator of problems 20 times faster than Velocity or Cycle Time related metrics.”featured in #533
The Magic Of Small Engineering Teams
- James Temperton tl;dr: “Startups ship more per person than big companies – everyone knows this. But how do you retain that advantage as you scale? Our answer is small teams – speedy, innovative, and autonomous one-pizza teams where individuals can still have an outsized impact. This week we're sharing how they work, why we chose this structure, and the tradeoffs we accept to enjoy the benefits of small teams.”featured in #533