Tanner Hodges

Relearning the obvious. Podcasting #webperf stories @CatchingUpDev.

🐘 @[email protected]

[Matt Pocock @mattpocockuk]

Instead of waiting for a new model to fix your problems

Why not just fix your problems

[Mario Zechner @badlogicgames]

Recommended reading.

But out of the old will come something new. The only thing that needs fixing is the dependency on big labs. I'm not sure it can be, unless they become true commodities.

https://t.co/4DZ9c1CYwC

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[Tanner Hodges @atannerhodges]

It's been a while. https://t.co/ODLRMaWHIo

[Tammy Everts @tameverts]

INP replaces FID as the responsiveness metric in #CoreWebVitals on March 12.

Let's revisit important INP research, starting with @cliffcrocker 's investigation into whether INP correlates to user behaviour. (TLDR: it does, but with caveats.)

https://t.co/1JCac23qIK #ux #webperf

[Tanner Hodges @atannerhodges]

@patmeenan @HenriHelvetica @SpeedKitcom 🙏 Awesome, I'll start poking around. Thanks!

[Tanner Hodges @atannerhodges]

What math formulas describe the load time of a web page? #webperf

[Tanner Hodges @atannerhodges]

@nomsternom 🤘 I love it. Got my wheels turning again.

[Noam Rosenthal 🦋 nomster.bsky.social @nomsternom]

Poor webperf rarely comes in isolation. it’s often accompanied by UI bugs, security issues, awkward auth flows, neglected a11y….

That’s because perf is an aspect of software quality, not a “feature”. Investing in webperf is one of the indicators of software quality.

[Tanner Hodges @atannerhodges]

@DanShappir Yeah, I can only imagine what a "universal formula" would look like (🤯) but what about more basic formulas, ones that model specific aspects of page load? — I'm looking less for accuracy and more for principles.

[DebugBear @DebugBear]

Not sure how to get started with web performance?

Check out our new blog homepage: https://t.co/k30TwQsKDW

[Brian Lovin @brian_lovin]

I can not stress enough how tough it is to build a web app that works well across browsers, mobile devices, and input methods while staying accessible and performant.

Hug your frontend developer.

[Robin Marx @programmingart]

What I consider to be my ✨best talk ever✨ is now online!

"Resource Loading at the Cutting Edge" from @PerfNowConf dives deep into #HTTP3 resource prioritization, and how browsers, servers and tools support this critical feature (spoilers: not well! 👇)

https://t.co/AHMOhywDdN

[Vinicius Dallacqua @WebTwitr]

So happy to be part of this year's Performance calendar 🥳🥳. This subject is close to me as currently I'm digging through user metrics and bridging the server-client gap 😀

[Alexander Podelko @apodelko]

My post 'The Golden Rule of Web Performance and Different Performance Engineering Specializations' in Web Performance Calendar https://t.co/9oVqgN7uMH @stoyanstefanov is doing that every December since 2009 - it is a treasury of #Performance info (mostly Web - but not only).

[Stoyan Stefanov 🪩 @stoyanstefanov]

🎇 And just like that, PerfPlanet calendar is a wrap with the "advent" part (24 articles in December). But rarely do we stop at 24. At this time the pipeline is empty, however I know some folks are writing and/or promised to write. I'll see when they deliver and either keep ...

[Stoyan Stefanov 🪩 @stoyanstefanov]

Perfplanet calendar article pipeline is almost dry. If you thought about writing an article, now's the time. If you didn't plan, now's a great time to think about what you'd like to share with fellow #webperf enthusiasts. Details: https://t.co/EROArp2Qsw and I'm here for any...

[Stoyan Stefanov 🪩 @stoyanstefanov]

🪩 Web Performance calendar day 9
👋 when @atannerhodges invites us to join https://t.co/ZlFpJQ5VW3 in addition to the webperf Slack
🔗 https://t.co/HcHxdzMLe3

[Stoyan Stefanov 🪩 @stoyanstefanov]

🪩 Web Performance calendar day 4
☕️ Let's cuddle by the fire with a holiday beverage of choice and let @EthanGardner guide us through warming up the cache for some delicious FCP and TTFB wins
🔗 https://t.co/dp030QiwLW