code@Stripe after work Water Polo Coach. Systems, People, Outcomes. Views are my own. co-host podcast.staffeng.com

• Pinned

  

  Happy to report that myself and

  @davidnoelromas

  are rebooting the Staff Eng podcast. podcast.staffeng.com/posts/were-bac… This next season will focus on AI. These tools promise 10-100X productivity gains, but many engineers (and other practitioners) don't know how to learn them—especially

• 

  New episode:

  @JWondrusch

  from Block joins me and

  @davidnoelromas

  to talk about what actually changes when agents get good enough to do the work. The 60-service monorepo migration that convinced him the ceiling moved, and why "raising ambition" is now a real coaching conversation.

• 

  You're all 100x engineers...now what? > frontier models might make you a 10x engineer but they also give your org all the problems of a company 10x bigger. The security debt, the audit trails, the blast radius. You move faster and inherit more. Checkout the Latest Staff Eng

• 

  Formal verification might allow LLMs to write safer code, but it's not 100%. From "Lean proved this program was correct; then I found a bug." Overall the code base was well crafted, but: > The two bugs that were found both sat outside the boundary of what the proofs cover.

• 

  From the skill: > The most important section is Drafted vs Sent. Every time you rewrite an AI draft before sending, save both versions. The gap is the voice. Smart. It's a mini self improvement loop. github.com/getlago/inside…

  

  If you're looking to improve your writing game, Anh is one of the most consistent heavy hitters I know in devtools HN and she literally just open sourced her writing Skills template for you to use below!