HeyJaredElevate
Addy Osmani's newsletter on elevating your effectiveness. Join his community of 600,000 readers across social media.
- Indexed issues, last 90 days
- 10
- Latest publication
- Sep 28, 2026
- Audience
- Checking…
- Earliest in this view
- Jul 3, 2026
Latest issues
The Code Nobody Reads (opens the original)
Read excerpt
Two years ago I wrote an essay about AI-assisted coding, and one of my tips was to review every line of generated code. I’d give that advice very differently today. What I’d say now is this: you don’t need to read all the code. Every change still needs some review and every change still needs a person who owns the decision to ship it. What’s changed is that a careful human read of every line is no longer the only way to provide that review, or always the best one. Some can be primari
Brownfield Agentic Engineering (opens the original)
Read excerpt
Agentic engineering in an old codebase is about making hidden constraints visible and cheap changes trustworthy. Let’s talk what to do in brownfield codebases.During my career I’ve worked on teams whose codebases had been around a long time. Those are brownfield systems: the repository is no longer a complete description of how the thing actually behaves. Institutional knowledge, duct tape, legacy services, and expectations other teams depend on live outside the tree. You have to learn those con
Agentic Skill Decay (opens the original)
Read excerpt
Mastery still comes from doing the reps.Before agents, I got my reps as part of writing code: try different approaches out, debug what went wrong, review other’s code, read a lot. Agents can skip much of that work, so building your reps has to be deliberate.If I was new to the industry, I’d try to form a hypothesis before prompting. Ask “why” a lot, read the diffs, try to predict what might fail. Occasionally try to work through the problem myself manually.<a class="image-link image2 is-viewable
Audit your Agent files (opens the original)
Read excerpt
TL;DR: Your coding agent’s configuration has a half-life. Models improve, harnesses add capabilities, codebases change, and the instructions we wrote for an older version stay behind. Recent research finds inconsistent value from personalized skills. I now run Claude’s /doctor every few weeks, review memory separately, and ask each instruction to earn its place again.I feel like there’s been a lot of confusion about skill files and what to do with your CLAUDE.md and AGENTS.md files, especially a
Human judgment doesn't leave the software factory. It relocates. (opens the original)
Read excerpt
A software factory is a repeatable loop around software work. If you’re building a software factory, code good enough to ship still needs human taste and ownership. We’ll discuss this including whether you need a factory just yet.If so:You’ll likely need humans in the loop upfront for deciding on product intent, system design (if you care) and your quality bar.Do review code (lights-on factory) but be intentional with where it’s needed the most. I
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.