This is the only AI I want to use

This is some code for SolidJS. Now,

notice I'm using signals incorrect. I

should be using the show component. We

wait for the LLM. And boom, we have the

show component. So, what you just saw is

a little project I call 99. And the

reason why I haven't kind of been

pursuing 99 is because I don't really

feel like I fit in today's kind of

modern world of AI. And let me explain

that. On one side, you have the no AI

side. I've always kind of been

interested in AI since day one. I've

played around with it. have saw a lot of

the sharp edges. I highly still

recommend to people that if you're

building production apps, you should be

just knowing and understanding every

single line of code you produce. Uh be

very careful. Please don't vibe code

production apps that especially that

take people's information out there.

Okay, it's going to end oh you know

horribly. And then on the other side you

have obviously the vibe coders, the

people that are out there just producing

raw code and who knows what kind of the

consequences or problems that actually

exist in between there. I obviously like

programming. Okay, I enjoy the actual

raw activity. I know there's people out

there like, "Ah, it turns out

programming was never the thing I

liked." No, programming is in fact the

thing I like. But more importantly, I'm

actually a pretty terrible reviewer.

When I actually am reviewing other

people's code, I am not that good at

seeing the problems and all that. It

takes me a long time to really review

the code. So, when an AI generates a

bunch of code, like a single piece of

code that would have taken me, say, 15,

20 minutes to write takes me maybe like

an, you know, a half an hour to review.

That's not obviously always the case,

but I I've never just been a strong

reviewer. And maybe that's a skill I

need to get better. And so I've always

kind of just lived in this world where

okay, well, I don't recognize and I

don't really identify with the no AI

people, but I'm certainly not a v viber.

So what should I be? And for a long

time, I was kind of this autocomplete

and that's it person. Like I loved tab.

Cursor tab I'd argue is one of the best

in the game. Okay. Uh game recognizes

game. That thing is actually incredible

what they have built. Huge fan of Super

Maven and everything that they have

done. But I've always wanted more,

right? Like, how do I take advantage of

all of this super fast generation of

code? But how do I make it do it the way

I want to do it? Is there a middle

ground that's somewhere between the tab

world and the vibe world? I think I may

have created it. That little example you

saw at the beginning was called 99. It

is my attempt at really trying to create

an experience programming that takes

advantage of AI but still puts me first

in the driver's seat because I have this

thing called lack of skill issues when

it comes to programming. I can actually

program. I have talent and and stuff

built up for many decades at this point.

So that means I kind of know what right

generally looks like and I'm can direct

an AI really fast if I can direct it in

a very fine grain way. So let me give

you a couple kind of like little

examples of what's going on. So, one of

the first things I can do is I can just

take this entire thing right here, which

is just a Cloudflare worker, and I can

just say, "Hey, convert uh this

Cloudflare worker to Hono." And notice

that it highlighted Cloudflare right

there. It identified on my machine I

have a skill called Cloudflare. So, it's

actually going to go through and make

sure that it actually uses all the

information about Cloudflare and then

convert it to a Hono worker. You can

even see right here, this is its

internal dialogue or whatever you call

that. I'll convert this Cloudflare

worker to use Hono. Let me write the

converted code to a temp file. All

right, there you go. We've converted it

all. Uh, is this good? Is this bad? I'd

have to review it, but you can see that

I can do a really large change to the

code base pretty easily. But this is

where I think it's actually a lot more

interesting. Let's say that I have

something called a game container, which

I do in this situation. It's Vim Royale,

and I want to be able to create a

matchmaking server. And I want this

server to be kind of like a stateless

one. One that I don't actually have to

have say a running durable object, but

instead I use D1 the database offering

as a means to do this. No, this is not a

sponsored post. This is not any of that

crap. This is me just trying out various

Cloudflare utilities. All right, so the

first thing I need to do is actually

create like a N variable. So I'll create

a m a matchmaking interface. jump in

here, take that and just go uh

Cloudflare end with D1, which is the

database uh the Jawat uh session. Let's

see. End um the game container. There we

go. Write those things out. It's

creating me a nice little end. Then I

can go export async uh function. What is

it? What are we going to call this? Get

game. We can have the ID as a string.

And then we can do a promise uh promise

game state. Now, notice that it's

actually going over there and it's

actually creating the stuff for me. So I

don't have to worry about that. Here I

can just be like return game state from

a games table. Uh using Cloudflare.

Notice I keep saying the word Cloudflare

because again I just wanted to use my

rules around it. It highlights it nicely

for me. There we go. Using Cloudflare.

Then I can go export a sync function set

game state uh GS game state and then hit

it with a promise void and then there we

go. So this is kind of what I really

would like uh using Cloudflare store

game. There we go. uh export async uh

function get all games. And so this one

right here should probably return a

promise. Oh, we should not call it all

games. Get um get uh joinable, right?

Joinable games, right? That makes way

more sense. And that should probably be

a game state with an array. All right,

so there we go. Game state with the

array. Jump in here and I can go like

this. Get games that are in a nit or

matchmaking uh for Cloudflare D1. Boom.

There we go. And now you kind of get

this idea. Like I've never actually used

a D1 in my life. I h I don't even know

what underlying database D1 uses. I just

know that D1 exists. I don't know how to

specify it. I don't know how to import

it. I don't know nothing. But yet right

here, I was able to grab all that

information. Get this bad boy right

here. Even though KV namespace is not

quite the right thing. It should be a

string, you idiot. And then of course I

can do something like this. I can do a

little get game right here. It's going

to go in. It's going to get the game.

It's going to do a little selection

right here. Pretty fantastic. Beautiful.

I don't, you know, would I throw an

error? Probably wouldn't throw an error.

Probably find a better way to do take

care of this. Set game state. This all

looks really, really good. This is

exactly what we're talking about. Get

joinable games. We're going to have to

do a select ID from where in initialized

or matchmaking. This is exactly kind of

how I would do this. The only big

difference I would make is this right

here. I'd much rather actually use the

game, the server game states as opposed

to just simply like raw dogging it right

in there. All right, let me create two

last functions and we'll have kind of

matchmaking done. I'll do a little

export async function. Uh create new

game. Actually, we don't want to export

this one. This one's only for us. Okay.

Uh and this should probably return a

promise of a game state. And we can go

like this. Just uh create game to create

a new game and return out the game state

after saving it to the uh D1 uh

CloudFlare. Boom. Nice. Async export

async function. Um, join game returns a

promise of a game state. Nice. That's

going to be right in here and go like

this. I had to kind of specify this one.

Uh, join the highest player count uh

server with matchmaking as the uh state.

Two, wait for a game server with state

of matchmaking.

Uh, three, create a new game if one and

two cannot happen. Cloud flare. Boom.

Tag it with that scale. And there you

go. So, as you can see right here, we're

creating the environment right here.

We're doing this bad boy right here.

Okay, we have this nice little set game

state right there. Perfect. And then we

can join the game right afterwards. Wait

naturally for what happened there. All

right. And this code right here, as you

can see, very weird numbering system. A

little 1 2 1 2 3 classic 1 2 1 2 3. So,

this is my ideal version currently of

AI. Uh, it just it kind of gives me that

control that I want where I'm also

having the speed, right? I'm determining

kind of the API how things should be

called. I can see kind of the building

blocks. Okay, I want like a a get and

set game. Then I want to be able to get

joinable games. I want to be able to

create new games. And then I want to be

able to join games. So I can kind of

like structure the code how I want. And

then I can actually have it generating

as I'm kind of structuring the code how

I want. Then I can kind of go back

through and fix little each little

piece. It just feels faster because

instead of being handed this just giant

diff of code, instead I'm just

generating one chunk at a time precisely

the chunk that I want to be generated.

Then I can also add these kind of

skills. I don't even know why they call

them skills. I'm not really sure what it

is. I'm not even sure if it really is a

skills. Okay. Uh let's go. Personal

skills. Skills. Cloudflare. This one.

This is really just me saying, "Hey,

this is how I want things to be

formatted. This is how I expect you to

be able to do things. I want you to be

able to create an env object every

single time. If you're going to be

creating uh anything to do with

configuration, I want you to specify it

this way. But at the end of the day, is

this the best AI? I mean, I think

there's a real world out there where uh

things are just going to continue to

improve and at one day people who hand

program will be the dinosaurs. Like

that's is this the time where people are

trans, you know, transferring from

handwritten machine code into compilers

and I'm over there like you boys are a

bunch of right? like, oh, is

that is that what's happening to me? I

actually can't tell. Will there still be

room for these type of tools, this

intermediate space that I'm talking

about? Will this actually be useful?

Maybe maybe people will really like

this. And maybe there does exist a world

for quite some time where people still

want to hand roll their code. Like me

personally, I'm just I'm just a bigger

fan. I like to know what's going on. And

perhaps that's an insecurity on my

behalf. I don't care what you guys have

to say, honestly. This is me just trying

to figure out and navigate this kind of

confusing world because at the end of

the day it is a weird rule. Like can you

fully trust a vibe coded app? Absolutely

not. Are people actually being able to

review 10,000 lines of code a day?

Absolutely not. When someone tells you

that they're lying to your face. And so

there's a lot of questions that I have

about this entire universe and how it's

going to look over the next couple

years. I think the next couple years are

going to be pretty dang complicated.

Anyways, if you want to give this thing

a shot, it's called uh 99 is what I

called it. We have uh some decent

contributions going. It's still pretty

kind of sharp edges. The skills thing is

just kind of landing on a separate

branch that I call skills version two

cuz I already had skills version one.

And I want to make still a bunch of

changes. Maybe I, you know, honestly, I

have a lot of thoughts about skills and

how they should be done. And I think

cursor actually got a lot of stuff right

really early on and I wish other people

would have followed their approach. But

nonetheless, this is me trying this is

me trying to make sense in a crazy world

that we have and still trying to really

understand actually programming and what

it's going to look like in 2026 2027. So

give it a try. Uh by the way, if you're

watching this video a little bit later

today, I'll be doing a live stream and

I'll be kind of fielding some requests

for various new features, what people

think should be done. I have some ideas

about debugging and semantic search that

I'd really like to add to the codebase,

but right now I'm just kind of focusing

first and foremost on just the uh

creation side of it. Can we get in code

generation? Anyways, I hope you enjoyed

this video. This really is my current

dream AI. Yes, I will never be as fast

as those people that just Dario take the

wheel the vibe coding. I hope you

enjoyed the video. Uh please leave a

comment and tell me like honestly real

talk is there room in this world for

this type of plugin? I don't know. May

maybe this is one of those things where

I'm the one being delusional. I think

that somehow I can maintain my own

agency in the world of agents doing all

the coding and I'm just kind of delaying

the inevitable. Or maybe I'm just trying

to make something fit that doesn't need

the fit. I honestly don't know and I

don't know if this plugin is going to be

great longterm, but it's just me trying

to make sense of the real world. And I'd

love to hear your thoughts on this. Do

you actually think there's a world where

this can thrive? But either way, this is

my ideal AI setup. And I hope you

enjoyed the video. The name is the 99

Agen. For those that don't know, I

actually named the library after this

right here, the Halo sniper rifle, the

SRS9.

Uh, and that's because I kind of looked

at the world and it kind of seems like

AI is like a shotgun. You're just

blasting everything. Not really a lot of

aim. Shoot from the hip. Whereas like a

sniper rif, you got to take it. You

know, you're actually thinking through

things. is you got one shot, one bullet,

one target. And it's a bit more of a

thoughtful kind of approach as opposed

to just like the spamming make anything

happen kind of approach, not the spray

and prey. So that's why it's called the

99.

Hey, do you want to learn how to code?

Do you want to become a better backend

engineer? Well, you got to check out

boot.dev. Now, I personally have made a

couple courses from them. I have live

walkthroughs free available on YouTube

of the whole course. Everything on

boot.dev you can go through for free.

But if you want the gamified experience,

the tracking of your learning and all

that, then you got to pay up the money.

But hey, go check them out. It's

awesome. Many content creators you know

and you like make courses there.

boot.dev/prime for 25% off.