Removing Uncertainty: The Tip Of The Iceberg
- James Stanier tl;dr: “When you’re staring a huge, challenging project in the face, don’t align your team around just getting it done. Instead, align your team around continually reducing uncertainty…” James advises us to prioritize the most uncertain parts of the project and focus efforts on getting answers. Answers fall into two broad categories: that it is possible, as proved by code, or that it’s not possible, but yields another avenue to try. You repeat this process until you’re done, or until you think it’s best to stop. “Focussing on reducing uncertainty builds momentum and trust both inside and outside of the team.”featured in #392
Identity-Native Infrastructure Access
tl;dr: Download your copy and learn how to prevent breaches by eliminating secrets, including the two new chapters on Secure Connectivity and Authentication.featured in #392
featured in #391
How We Manage Incident Response At Honeycomb
- Fred Hebert tl;dr: This article is broken down into five sections that provide a coherent view of incident response: (1) Dealing with the unknown. (2) Managing limited cognitive bandwidth. (3) Coordination patterns. (4) Maintaining psychological safety. (5) Feeding information back into the organization.featured in #391
Build Internal Tools, Remarkably Fast
tl;dr: Build business software 10x faster with Retool. Companies like Amazon and DoorDash use Retool to build apps and workflows that help teams work faster. Retool is free for teams of up to 5, and startups can get $25,000 in free credits for paid plans.featured in #391
featured in #390
The Only Guide To Automated End-To-End Testing You’ll Ever Need
tl;dr: If you’re looking for automated test coverage, there are a few options to consider: in-house, traditional outsourcing, or Test Coverage as a Service. We wrote this guide to help you find a solution that aligns with your product, team size, budget, and overall testing needs.featured in #390
Writing An Engineering Strategy
- Will Larson tl;dr: Will discusses: (1) An example of an engineering strategy. (2) Richard Rumelt’s definition of strategy: diagnosis, guiding policies, and coherent actions. (3) How and when to write your engineering strategy. (4) Dealing with undocumented strategies in other functions. (5) Structuring your guiding policies around resource allocation, fundamental rules, how decision are made. (6) Maintaining the right altitude in your strategy by ensuring guiding principles are applicable, enforced, and create leverage. (7) The most common kinds of coherent actions in engineering strategies. (8) Whether strategy should be executive-lead.featured in #389
Saving Millions On Logging: Finding Relevant Savings
- Rich Marscher tl;dr: "At HubSpot, our relatively new Backend Performance team is tasked with improving the runtime and cost performance of our backend software. In this two-part blog series, we will look at a structured method we use for approaching cost savings work and demonstrating how we apply it at HubSpot to save millions on the storage costs of our application logs.”featured in #389
featured in #389