You’ll learn

• Engineering teams often over-build for ambiguous future problems that never actually arrive. Build for today's problems to avoid painting yourself into a corner with unnecessary infrastructure.

• When the cost of a new service is nearly zero, developers will naturally choose to spin up new ones instead of digging into existing code. This creates a cognitive tax that slows down onboarding and makes working across teams feel impossible.

• Technical metrics like release frequency are helpful for spotting anomalies, but they don't tell you if you're heading in the right direction. True productivity should be measured by business KPIs like payment success rates or accuracy of results.

• Context often gets blocked as it trickles down from the C-suite to the individual contributor. Small roundtables with mixed groups are more effective than large all-hands meetings for identifying where that context is getting lost.

• Leaders should look at the hard data but also pay close attention to the anecdotes and sentiment of their teams. If the metrics look good but the customers or engineers are unhappy, you've still got a problem to solve.

Timestamps

• 01:08

  Defining microservices as a trillion dollar mistake when they're over-engineered.

• 04:00

  How zero-cost service creation creates an incentive model that backfires.

• 12:04

  Identifying the macro tax of architectural complexity during critical incidents.

• 13:58

  The cognitive tax that every developer pays when navigating a complex ecosystem.

• 19:34

  Breaking down the difference between "miles per gallon" metrics and actual outcomes.

• 28:54

  Why uptime is not the be-all and end-all for every business.

• 33:36

  Managing the game of telephone between leadership and individual contributors.

• 41:48

  Using small roundtables to identify and fix communication blockages.

• 46:28

  Balancing quantitative data with qualitative sentiment to measure organizational health.