October 10, 2026
AI experience pays off when shared with the team: Addy Osmani's advice
On Oct 10, 2026, Addy Osmani wrote that if a team is only allowed to try AI after work, it “doesn’t count.” Senior engineers, in his view, should go first and show others what works.

Addy Osmani
@addyosmani
Your edge right now is understanding what’s possible and staying curious. Using AI in development is now the default. Engineers who have an edge are ambitious and have worked with agents on the job for years. It’s the compound interest effect. For teams that are still hesitating or falling behind, I’d offer the most sensible advice: be more ambitious and actively share your findings with colleagues. If you do all this work alone, only you benefit. If a team only tries AI after work, you’ve quietly signaled that it doesn’t count. Senior engineers should take this step first. A decade of taste for system design and knowing how things break is what makes agent output good. Let them point their experience at making agent work safer. Then let them show the rest what works so others can repeat it.
🗞️ if your team is too busy doing their 'normal job' to experiment with AI, you're preparing them to be replaced https://ghuntley.com/replaced/ In this post, I guess this's the last time I'll say it. AI use is no longer optional if you wish to be employed. What follows is advice for current employees and hiring managers on how to hire in 2026 to source AI-first candidates.

· 37.4K views
According to Osmani, using AI in development has become the default, and anyone who has worked with agents for years builds an advantage like compound interest. In his Aug 31, 2026 breakdown of about 400,000 Claude Code sessions, experience on a task raised the odds of a verified result compared with newcomers.
A trap for learners. In an Anthropic study that Osmani reviewed on May 16, 2026, junior engineers with an AI assistant scored 50% on a quiz about the Trio library, while those who worked by hand scored 67%, in the same amount of time. The best results went to those who asked conceptual questions rather than copying code.
In his May 16, 2026 breakdown, Osmani names five situations where delegating to agents breaks down: debugging failures, catching hallucinations, framework upgrades, non-standard tasks and competition in the job market.