Original post on pony.social

pony.social

Leaving Mozilla

> On burn-out and bull-headedness

blog.unitedheroes.net

Meow

Meow meow meow meow Meow Meow Meow (MEOW). MEOW meow meow meow meow-meow meow meow meow Meow meow meow, meow meow meow meow meow meow meow meow meow meow meow meow meow Meow. Meow meow meow, mrrp meow meow meow meow meow meow meow MEOW meow meow meow meow meow MEOW MEOW, meow meow meow meow meow meow meow mrow meow meow. Meow meow meow meow meow meow meow meow meow meow meow meow meow MEOW MEOW. Meow meow meow MEOW MEOW, meow meow meow Meow MEOW, MEOW, MEOW, MEOW, MEOW, meow MEOW meow meow meow meow MEOW MEOW. Meow meow Meow MEOW meow MEOW, meow meow meow meow meow meow moew meow meow meow meow meow meow meow meow meow MEOW meow. Meow meow meow MEOW MEOW meow meow nya meow meow meow meow meow meow meow meow MEOW-MEOW meow. Meow MEOW meow meow meow meow MEOW MEOW meow meow meow meow meow meow MEOW MEOW.

ietf.org

Just because it's work shaped doesn't make it productive

AI Assisted/Agentic programming are pretty common place at this point. The growing sentiment seems to be that if you can't find some sort of benefit in your workflow, it's more of a skill issue than a problem with the tools. Whether you believe this to be true is really up to you, what is clear is that it's becoming more of an expectation than an option for many engineers. Agent led development is showing foreseeable (and increasingly well documented) costs that developers promoting the hype cycle continue to ignore 1. Poor/weakened skill acquisition - Particularly in junior talent that we should be cultivating 2. Skill atrophy - Particularly in more senior engineers, when you don't use a skill you lose it. I wrote more on this recently. 3. Comprehension debt - Engineers are supposed to be reviewing code but many aren't. Things slip through the cracks. Systems change at a pace that teams cannot keep up with. In the end they may know what it's supposed to do, but do not why or how it works. 4. System bloat - Since generating code is cheap, creating code that shouldn't exist becomes the default solution to problems. 5. Insufficient quality gates - The speed at which code can be generated will always outpace the speed at which it can be reviewed. Larger PRs decrease the likelyhood that the code will be reviewed correctly. DORA associates larger PRs and increased review times with worse outcomes. These are all subjective and apply differently to different situations, but it's unfortunate to see so many engineers willing to throw away known good fundamentals and replace them with practices that vendor lock-in their skill with a productivity heavy tail. I should be clear that there's a lot of value to be gained from using these tools, but I'm not convinced that layers and layers of AGENTS.md, SKILLS.md, with dozens of agents generating code in the background is the way to derive it. Thoughts on slowing the fuck downThoughts on slowing the fuck down It's extremely easy to get trapped in a cycle attempting to automate a process which ultimately ends up needing its own documented process and maintenance upkeep. Historically, simpler tools and processes have had the most staying power That said, I'm seeing grumblings of influencers reporting on their own first hand experiences so maybe the tide is turning. > The more I use AI tools, the more I have to admit that I'm not that much more productive... I simply FEEL that much more productive. In reality, the context switching of kicking several things off wipes out my perceived productivity gains. At least in many/most cases! > > — Gergely Orosz (@gergely.pragmaticengineer.com) April 3, 2026 at 10:55 AM

nishtahir.com