Great list of resources here by Pete Steinberger:

These resources will help you master the new paradigm of AI-assisted development, where agents become true collaborators that can handle entire codebases and ship production features. Each piece was chosen for its practical, real-world insights.

I especially appreciate that it’s a combination of articles (yay!) and videos (not for me!), and that he provides a nice overview of each so you can decide if you want to click through or not. Excellent curation, would recommend!

Read Essential Reading for Agentic Engineers ↗

This take on the Pocket shutdown resonates with me real hard:

“What began as a read-it-later app”, they assert, “evolved into something much bigger.” That was the whole problem: the mistake that led ultimately to this “difficult decision” by Mozilla. Pocket was a good tool. Its integration with Kobo, another excellent tool, made it that much more valuable to users like me. We didn’t need “something much bigger”. But by trying to turn Pocket into something much bigger, Mozilla actually killed it.

I feel like nothing has changed since I wrote about this kind of thing in… 2012:

This is the core of the disappointment that many of us feel with the Sparrow acquisition. It’s not about the $15 or less we spent on the apps. It’s not about the team’s well-deserved payout. It’s about the loss of faith in a philosophy that we thought was a sustainable way to ensure a healthy future for independent software development, where most innovation happens.

→ Some Products Just Aren’t Big Companies

Great advice here for new managers in this wild time we find ourselves in. In general:

Whereas the previous focus of managers was to rapidly hire and scale their teams, today’s focus is on expanding impact. This is because in today’s macroeconomic environment, output is key. In the eyes of a 2025 company, the more that you can do with fewer people, the better. There are very few additional people to go around, so the focus is on how you can help your team do more with less.

James focuses specifically on EMs, but the advice definitely applies to PMs too, so check out his post if this is you!

→ New advice for aspiring managers

I’ve been thinking about engineering estimates a lot and need to write about it. But for now, Adam Keys sums it up nicely:

Everyone knows surprises will happen. The estimate should help the team make better decisions when they do, not box them into promises they can’t keep. The best estimates I’ve given weren’t the most accurate—they were the ones that helped teams navigate uncertainty instead of pretending it away.

→ On estimates as navigation, not promises

Ok I love this story.

I’ve been reading a lot of Robin Wall Kimmerer lately. She tells a story in The Serviceberry that’s become a sort of guiding star for me, about the experience of a linguist who was studying a hunter-gatherer community in the Brazilian rainforest.

“He observes that a hunter had brought home a sizable kill, far too much to be eaten by his family. The researcher asked how he would store the excess. Smoking and drying technologies were well known; storing was possible. The hunter was puzzled by the question […]‘Store my meat? I store my meat in the belly of my brother,’ replied the hunter.”

And yes to this:

I’ve been thinking so much about what it would mean for me to “store my meat in the belly of my brother”—to give to my loved ones and communities and trust that my generosity will circle back to me when I need it. I know it’s how I want to live. It’s how I want us all to be able to live.

→ Interdependence is My New Retirement Plan

Great tip!

Convert GitHub repos to markdown with repo2txt, drag into Google AI Studio, and ask questions. Gemini’s massive context window makes it amazing for code comprehension.

The rest of the article goes into Peter’s AI coding workflow. I’ve mostly been using ChatGPT o3 for spec creation, but this is another compelling alternative.

→ My AI Workflow for Understanding Any Codebase

I know we’re drowning in vibe coding stuff right now, but this extensive post about shipping code with Claude is a fantastic resource. Great prompt rules and tips, and also solid advice for what the humans are for…

Your role as a senior engineer has fundamentally shifted. You’re no longer just writing code—you’re curating knowledge, setting boundaries, and teaching both humans and AI systems how to work effectively.

Lean management and continuous delivery practices help improve software delivery performance, which in turn improves organizational performance—and this includes how you manage AI collaboration.

→ Field Notes From Shipping Real Code With Claude

This is great advice on providing feedback on docs. This especially resonated:

Before starting, remember that the goal of providing feedback on a document is to help the author. Optimizing for anything else, even if it’s a worthy cause, discourages authors from sharing their future writing. If you prioritize something other than helping the author, you are discouraging them from sharing future work.

→ How to provide feedback on documents.

I love this take on the “10x engineer” phenomenon. Ubuntu (the African concept, not the operating system…) strikes again. “I am because you are.”

Individual engineers don’t own software; engineering teams own software. It doesn’t matter how fast an individual engineer can write software. What matters is how fast the team can collectively write, test, review, ship, maintain, refactor, extend, architect, and revise the software that they own.

→ In Praise of “Normal” Engineers