These are one of those things where I

just I could have never predicted. I

could never have predicted it in a

million years. Even if you gave me so

much of the information leading up to

this point, I just would not have been

able to make the guess. It all started

with this video right here. Pewdiepie

deciding to embrace the Linux and even

more importantly the Arch Linux

lifestyle. And then he started to do a

little bit of hardware. And it was it

was amazing to watch kind of his process

of 3D printing and getting all the wires

inside the compartment and everything

actually working. Then eventually he

makes this a supercomput in which he

puts a bunch of AIs on it and actually

makes them all come to consensus and

have some sort of competition with each

other. And he calls it the council. And

then finally, PewDiePie goes out there

and attempts to train his own coding bot

and spends days upon days generating his

own data, having to figure out how to

make actually clean data, not

accidentally poisoning any of his tests,

and ultimately make it so that he can

generate a robot that has a better score

than some of OpenAI's older models. And

it's just not something that I would

have guessed would have happened in

2026. I know these last few years, the

writers, they've been really, really

good. They're just setting up every

season better than the previous. The

guesses, the twist, the turn. I would

have never guessed any of it. But this

for me was the most surprising. Watching

somebody who I largely thought was just

a goofball on the internet turn into

actually a legendary kind of engineer

who's building things and actually

learning and taking his time and

embracing failure. And it's really

strange to say this, but I felt like I

need to say this. I think there's a lot

we can all learn from feuds. Yes, Mr.

Ligma himself can teach us all a good

lesson. So, I'm going to do a lot of

yapping and we're going to do a lot of

yapping about what Peudes has said. But

first, I think you should just probably

hear it straight from him. We're going

to jump in at the end of a video in

which it is PewDiePie talking, you know,

through all of his thoughts after going

through this really long process of

creating his own supercomput, getting

into AI, and then ultimately training

his own to be able to be good at a

coding benchmark. and he went from not

knowing anything about coding to

actually taking courses on boot.dev. I

think he it's like boot.dev/piedy. And

it's an incredible journey to watch

somebody go from not knowing anything

just like a guy who played video games

to actually building and finishing

pretty amazing projects. And this is

what he had to say. You've seen me fail

a lot in this video. I have become so

accustomed to failure. You have no idea.

I've almost given up on this product so

many times. There are so many times

where I was just like, I don't know what

I'm doing. This is the stupidest thing

ever. I have graveyards full of just

garbage, debunkle, schmunkle, deformed

data that I have generated thinking this

is the best. [laughter]

I have gone through the whole alphabet

of failures. I was just so way in over

my head on this project. But I think the

number one thing I've learned, how do I

explain this? When you install Linux,

here's what happens. Linu Toval the

creator becomes your godfather

inevitably and I was watching one of a

random video of him talking and he was

talking about how he's doing this

project and he was failing but that's

okay because that's how you learn. Uh

some people think that failure is a bad

thing and I happen to be one of those

people who actually

enjoy doing

things I'm not good at

because it's how you learn. And I'm

watching that lad and I'm like he's

speaking to me right now.

Oh my god. But I really feel like that's

the main thing I've learned from all

this because there's so much to learn

from failure. Learn from it and iterate

and keep working. I think if you have

expectations of how things should go for

yourself, you're just going to get

disappointed and you're going to want to

give up. So expect to fail, embrace

failing. That's the message I want to

send out to you kids. The reason why

this kind of spoke to me a lot is is one

of the very first things I was ever

taught as a computer scientist. Right?

You may have heard of this. A computer

scientist is the dying breed. It's

someone who went to college to study

programming. [laughter]

What? Right. Uh anyways, my very first

class, I forget who was teaching it. I

want to say Shannon Shannon Willoughby,

but she was my physics teacher. Who was

it? I can't remember. or Ray Babcock

maybe. Anyways, he gets up and says,

"Okay, the most important thing I can

tell you is that you will fail. And when

you start seeing failures, read the

error message." There will be no greater

takeaway from this intro into

programming than reading the error

message. And that was something that

just kind of stuck with me for a very

long time is that I could just read the

error message. And once you start seeing

enough of them, all of a sudden errors

are just not all that bad. In fact, it's

kind of like a expected case as you go

through your programming journey from

idea into actual product. You know, as

the the old man on Twitter out here

yelling about coding standards and all

this stupid stuff, uh, you know, I just

I'm I'm just watching an entire group of

people that I feel are avoiding or

scared of the error condition, the

failure case. I see so many people start

a project, start going for a little bit

and inevitably because they've only ever

invested say in agents and the agent

coding lifestyle, they hit a wall and

then they just move on to the next and

the best thing and they don't actually

have the ability to push through and

understand the errors because when they

finally get to an error state, which

happens now much much later in your

journey than say for me which was just

like I wrote my first if statement and

boom, I'm already hitting errors cuz my

syntax was bad. There's just this terror

that I see among a lot of people when

encountering an error. I think what

PewDiePie said was the best is that

errors are inevitable. They should be

your expectation. They shouldn't be the

thing that surprises you. But more

importantly, it is the errors that

really shape you. every single error and

every single failure and every single

hurdle that you get over is something

that just makes you into a better

developer, someone that can build bigger

things, someone that actually can

understand bigger concepts. And you

shouldn't be afraid to get your hands

dirty and just learn. I know everybody

right now is going to tell you the

future is just learning how to pr and do

all these things, but I think there is

just so much value in knowing the why

underneath the hood. You don't always

need to move at 1,000 mph. I believe it

was Mary that once said shortcuts make

long delays. And you shouldn't just try

to shortcut everything. Try to be like

pudes. Take some time. Do a little bit

of learning. Now, I know for a fact this

is YouTube. This is a more global

audience and I'm going to immediately be

hit with, well, yeah, I guess if I was a

super rich millionaire, I too would take

my time to learn. But that's not my

case. Okay, true. You have a different

set of constraints than PewDiePie does.

Pewdiepie does have a set of time that

you simply don't have. Now, I can make a

bunch of arguments about why, say, how

many videos he's producing, how much

more time he's probably spending than

you realize on all these things, but

nonetheless, we can all agree he

probably has more free time than any of

us. But none of that prevents you from

taking 30 minutes to try yourself. None

of that prevents you from reading

online, generating tutorials, actually

trying to better yourself as opposed to

just continue to rely on this slot

machine that exists out there. Because

what I'm seeing the most and the thing

that I guess I'm I'm most nervous about

a lot of the upcoming generation, the

new the nextg developers is that they

don't know how to struggle because

struggling has largely just been taken

out of the equation. Ah, dang. How do I

make a Cloudflare worker? Oh, that's

how. Okay, go. Oh, how do I why is it

flickering? Oh, that's why. Okay. And

it's just like you don't have to

struggle. You don't have to go and read

things anymore. and you just say, "Hey,

fix it. No mistakes. Don't forget to

make it secure." And boom, it's done.

The struggle is gone. Now, I could bring

up the fact that it turns out agents in

real code bases spent over a long

periods of time are actually

experiencing larger amounts of failures

than you're being led to believe, or

that AI is actually increasing or

intensifying the amount of work you're

actually doing. I largely find studies

to be unconvincing. What really is

convincing is that I think more of a

positive argument, not an argument away

from danger, but towards something good.

Learning and struggling is just going to

make you into a better person. You're

going to become more patient. You're

going to become more resilient. You're

going to be able to take things further.

So, it's okay. You can turn off Twitter.

You can turn off the hype machine and

you can take 30 minutes and go learn

every day. And in one year, you will

actually make a dramatic difference in

your life. I would have never guessed

that this guy would end up being the

north star for mentality. But here we

are. Here's to 2026. The year you

actually take things deeper. You know,

you actually go harder. You actually

learn and you embrace the struggle. The

name is the primogen. Hey, is that HTTP?

Get that out of here. That's not how we

order coffee. We order coffee via ssh

terminal.shop. Yeah. You want a real

experience? You want real coffee? You

want awesome subscriptions so you never

have to remember again? Oh, you want

exclusive blends with exclusive coffee

and exclusive content? Then check out

cron. You don't know what ssh is?

>> Well, maybe the coffee is not for you.

Terminal coffee [music]

in hand.

Living the dream.