How I build.

What you see in this animation is my control room. Right now it's only a drawing, but in about forty minutes it will be a real, working website on a small server in Amsterdam. Simply reachable over the internet. And I won't type a single line of code for it myself. I give Claude an assignment and it builds everything itself. Want to know how this video was made? Then wait until the end. I'm starting the clock.

I'm Jacob. I've worked in IT for 12 years. I started on a service desk, then did 7 years of system administration. On-premises and in the cloud, for mid-sized and large companies. The cloud became my specialisation. Mostly Microsoft Azure. And now I run my own IT training company. I don't really program. I do script. With PowerShell I manage Azure and server environments. But building a complete website? I've never done that. What I do understand is everything around it. Hosting, version control, security.

And with Claude I now simply build the apps for my business myself. Today: a control room. One screen where I can see which of my web apps are running, whether they're secure and who is logged in. I'll show you what happens, even if you don't program yourself.

This is Claude Code on my MacBook. First I create a new project in an empty folder. Then I paste in an assignment I prepared specially for this demo. And I put Claude in plan mode. That way it first calmly thinks through a plan before it builds anything.

And then it does something I find really useful to include. It starts five critics. Five separate AI agents. Each with its own role. A kind of critical colleagues. They read the plan and give it a score. Here they come in. One by one. Claude reads what they found and adjusts the plan. And then begins the part you normally never get to see.

The reason this is all going so fast right now is that my environment is completely prepared for it. One house style, so Claude doesn't have to invent anything itself. Fixed choices for the code, for the database, everything in git. And nothing goes out until all the tests have run. That yellow block you saw is one of those changes. Even the hosting is already connected.

And then it's mostly waiting. The clock in the top right just keeps running. And here I get a first look at the site. And then the tests. You can see them really running here.

All my other apps were built in exactly the same way, by the way. This is the portal for my Dutch lessons. Same shape. And the control room will be able to read that one too.

But things do go wrong sometimes. Here a test fails. There was an internal address in some text on the site. Claude fixes the text, and the test stays nice and strict. As long as anything is red, my deploy script simply refuses. The tools are fast, but whether it's right, I always want to see that for myself.

Before I put anything live, the same five agents review it once more, because I ask them to. Now they're looking at the control room itself. At screenshots of the site that's already running. What's unclear? What's still open? And they're not being nice. Three of the five saw right away that it didn't fit well on a phone. I read what they found, pick what I think matters, tell Claude, and it applies it.

Once I've approved it, the deployment itself. Claude runs my deploy script. First all the tests run one more time, and only when everything is green does it go out. A machine, a disk and a web address are created. Then it checks whether everything responds. And whether logging in works.

After 39 minutes I ask Claude whether the website is online yet. And sure enough, it's running on a real server with a real address. Here it is: controlroom.itkaro.com. I log in and take a look. The drawing from the start, but now for real.

I can simply ask it things, like whether the cockpit is up. And here you see my real calendar. I only blurred the names. And I ask how many people are in the language portal right now.

On Fly, one machine is running. And it goes to sleep when nobody's looking. And in the cockpit, the control room is now on the map of my environment too. Among the rest of my apps. With the check round I wake all the apps up and it checks them. 39 minutes, from an empty folder.

Well, to be fair. I had set up the address and the keys yesterday. And the foundation it builds on has hundreds of hours in it. These are the weeks that went into it. The build itself is fast, but the real work was in the preparation.

All those different layers you just saw. Security, version control, the infrastructure, hosting. I'll explain them one by one, in depth, here on the channel. Each part in plain language. Want to follow along? Then subscribe to the channel and give me a like.

Oh yes, one more thing. This video, with all the animations, I also made with Claude. In the video editor I built myself. This is it. I type what I want to see, Claude builds the animation and puts it on my timeline. Then I check whether it's right and does what I want. Usually it still needs some polishing, but I just give that as an instruction too.

Nice, right? And now I want to do this for other companies too. For five companies, in five days, I build one free app. And everything is recorded, like you see here. Would you like to be one of those five? Then sign up at itkaro.com.

Or would you rather learn it yourself? That's exactly what I'm here for. I explain it in plain language, whether you're a technician or the person who decides what gets bought. You learn it yourself. I'm right beside you.

And in the next episode: security. For me, that's the first layer of the foundation, before Claude writes a single line of code. And I'll show how Claude scans all my sites from the outside, every day, just like a real attacker would.