Brain Rot Or The New Normal
━━━━━━━━━━━━━━━━━━━━━━━━━━━

I watched through this video earlier of this guy roasting t3.gg and his level of agentic ai brain rot.

Date: October 1, 2026

I watched through this video earlier of this guy roasting t3.gg and his level of agentic ai brain rot.

https://youtube.com/watch?v=ZumXpZzDsgo

I really do think this guy had a lot of valid comments about people not being able to look at long form content, not being able to focus long enough to read a page of ai output. Losing our ability to think critically. He points to some of t3.gg’s videos at certain points where Theo says, I’m not even going to read this I’m going to have the agent xyx and move on.

The guy roasting Theo seems like a really smart guy, an academic kind of guy. A guy that really values knowledge. Mad props for this and his ability to avoid the brain rot. I think we have a lot of folks out there that are talking the talk without walking the walk. This guy seems genuine. He seems like he really knows what he is talking about and that he is still reading and writing every line of code himself.

I think we still need people that can carry this torch. It’s going to be a long time until there’s no need to hand code anymore. No need for someone who can hyper-optimize some critical part of the application.

Maybe thenewnormal
──────────────────

Thinking practically though. I think we are going to need a lot less of this. What we really need is someone who can translate real business requirements into action. For most people paid to write code the code is still not the key part of the output for the business. It’s an artifact used to drive value to its customers. How many customers do you think care about the code your company writes… Outside of a rare consulting firm or something that the job is to give code to another business it’s ZERO, nada, none.

Even a company like GitHub, I don’t care if the code is beautifully chiseled ruby or the most eye bleeding rust you can imagine. What I care about is uptime, features. Do the features I paid for work? Are the new features something that is going to matter to me? Is the service getting better or worse?

StAke_H_OldeRVal_U_e
────────────────────

The job is shifting from who can deeply understand the language and framework abstractions that are used by the team to who can move the needle the fastest. Who can ship features they can prove that work, quickly revert mistakes, see production issues, make quick decisions. They know the data we need ahead of time to spot issues, see how many users are being affected, how critical this issue is, and understand what action to take. Do we roll back, fix forward, keep monitoring, do we need to issue comms, to who, where?

I’ll leave you wtih this guy trying to respond to an incident in a hilarious skit.

https://youtube.com/shorts/otkUJ3RPlg8