Encoding team standards

Encoding team standards
13 minutes by Rahul Garg

Senior engineers carry unwritten rules in their heads about how code should be generated, reviewed, and secured. When AI tools depend on individual prompting instincts, output quality varies wildly across a team. The fix is to encode those instincts as versioned instruction files in the repository, so the team's judgment runs as shared infrastructure rather than personal habit. This turns tacit knowledge into something every developer can invoke, not just inherit.

Still writing tests manually? Meticulous AI is here.
sponsored by Meticulous

Most teams are forced to make the tradeoff between better coverage and more maintenance effort. But top engineering teams like Notion, Dropbox, Wealthsimple and LaunchDarkly have discovered a new testing paradigm. Built by ex-Palantir engineers, Meticulous creates and maintains E2E UI tests that covers every edge case of your web app - without any developer effort, making it the only tool to improve both product quality and dev velocity.

The cathedral, the bazaar, and the Winchester mystery house
12 minutes by Drew Breunig

AI has made writing code almost free, which is changing how software gets built. Developers now create sprawling, personal tools for themselves, like the Winchester Mystery House, built by one person, guided by passion, with no need for outside feedback. Open source communities still matter, but are getting flooded with low quality contributions faster than humans can review them. The real bottleneck now is not writing code but finding ways to manage attention and surface good ideas.

Dropping sprints: A year with shape up
14 minutes by Anton Zaides

Anton describes a team’s shift from Scrum to Shape Up after a company reorganization. Over eight cycles, the new approach improved focus, reduced interruptions, and increased delivery. Engineers gained more autonomy and satisfaction, while business teams became more involved in setting priorities. Challenges included scoping and handling large projects, but overall the method helped the team move beyond maintenance mode and deliver meaningful results.

The builder role
8 minutes by Dalia Havens

Deep specialization alone is no longer enough. The engineers gaining ground are those who own problems end to end, direct AI agents with clear judgment, and care about outcomes beyond their technical lane. Dalia argues the expertise still matters, but it now works best as the foundation for operating across a much wider surface area.

Who are you really competing against?
4 minutes by Noa Ganot

Most product teams can name their competitors in seconds. Fewer stop to ask what customers are truly choosing between in real life. In this post Noa revisits competition from the customer’s point of view and why that distinction matters.

And the most popular article from the last issue was:

• The economics of software teams