← Back
Theo June 12, 2026 56s

Do You Remember Me Before AI?

Read full transcript 1 segments
  1. A lot of y'all probably remember me from A lot of y'all probably remember me from a different type of content that wasn't a different type of content that wasn't a different type of content that wasn't very AI at all, create-t3-app. The goal very AI at all, create-t3-app. The goal very AI at all, create-t3-app. The goal of the T3 stack wasn't to get famous by of the T3 stack wasn't to get famous by of the T3 stack wasn't to get famous by having my tech take over the world, it having my tech take over the world, it having my tech take over the world, it was to be easier to build apps in the was to be easier to build apps in the was to be easier to build apps in the specific lazy way that I liked. I wanted specific lazy way that I liked. I wanted specific lazy way that I liked. I wanted to have my computer tell me when to have my computer tell me when to have my computer tell me when mistakes happened all across the mistakes happened all across the mistakes happened all across the boundaries that exist in my systems. The boundaries that exist in my systems. The boundaries that exist in my systems. The fact that my back-end code could tell me fact that my back-end code could tell me fact that my back-end code could tell me when there was an error between two when there was an error between two when there was an error between two functions, but my front-end code functions, but my front-end code functions, but my front-end code couldn't tell that the back-end code couldn't tell that the back-end code couldn't tell that the back-end code changed frustrated me deeply. T3 stack changed frustrated me deeply. T3 stack changed frustrated me deeply. T3 stack was built to rethink that, to get you was built to rethink that, to get you was built to rethink that, to get you the benefit with less effort in a more the benefit with less effort in a more the benefit with less effort in a more minimal way. To put it simply, an minimal way. To put it simply, an minimal way. To put it simply, an attempt at making the simplest possible attempt at making the simplest possible attempt at making the simplest possible set of abstractions that give you that set of abstractions that give you that set of abstractions that give you that full-stack type safety so that your full-stack type safety so that your full-stack type safety so that your computer will tell you when you make computer will tell you when you make computer will tell you when you make dumb mistakes. So, it was my hubris to dumb mistakes. So, it was my hubris to dumb mistakes. So, it was my hubris to think everyone should use a stack like think everyone should use a stack like think everyone should use a stack like this, and my impatience to not have to this, and my impatience to not have to this, and my impatience to not have to explain it over and over again, and my explain it over and over again, and my explain it over and over again, and my laziness to just want it in one place laziness to just want it in one place laziness to just want it in one place that led to this channel existing.

Summary

The T3 stack was created to simplify full-stack development by prioritizing type safety and developer ease, aiming to reduce errors and effort. The core idea centers on creating a minimal set of abstractions that provide the benefits of type safety across the entire application. The practical takeaway is that the T3 stack helps developers build apps more efficiently by having their systems proactively alert them to mistakes.

View original episode ↗