Skip to content
HeyJared

Engineering Futures

A weekly newsletter exploring the future of software engineering leadership in the AI era. Join 5,000+ engineering leaders rethinking how we build, measure progress, as the industry evolves rapidly. By the makers of Maestro AI.

Newsletter · By Justin Cranshaw · English · Official site

Indexed issues, last 90 days
2
Latest publication
Aug 31, 2026
Audience
Checking…
Earliest in this view
Jul 25, 2026
The latest indexed work is over 30 days old. There may be a gap in what we hold.

Latest issues

  1. Issue · Aug 31, 2026

    Not Every Problem Needs a Sledgehammer (opens the original)

    Excerpt

    Read excerpt

    “I spoke to an engineer at one of our suppliers who said that in the last six months, he’s generated a million lines of code.”Michael Frendo, the CTO of New Relic, offered me that as evidence of acceleration, one data point among several. The counterweight came from the start of his own career, at Nortel in Ottawa: “Our telephone switch at the time had the largest code base in the world. It was the largest. It was 14 million lines of code, and it had 2,500 engineers working on it for decades. No

  2. Issue · Jul 25, 2026

    AI Fails Like We Do (opens the original)

    Excerpt · Critical tone

    Read excerpt

    Ten minutes into our conversation, Sylvain Kalache drafted me into a role-play. “Let’s say I’m the SRE and William, you are the developer,” he said. Production is down. He runs git blame on the broken microservice and finds my name. “Hey William, how about you come sit next to me, or let’s jump in a Slack channel — maybe you can help me solve it.” That’s the oldest move in incident response: find the author, sit them next to the problem, let what’s in their head speed up the debugging. And git b

Publishing over time

Last 90 days. Choose a month to open its work.

Recurring subjects

Named in the text we hold. One piece can cover several.

Audience

No verified audience measurement yet.

About this data

Counts cover the work we have indexed. Tone needs enough text and a confident classification. Excerpts and episode notes are not full articles or transcripts.

Identity or attribution wrong? Suggest a correction.

See coverage about Engineering Futures