Listen

Description

This is a story from the frontlines of coding in the AI era. I'm a real builder, not a vibe coder, and I'm going to explain the difference in a real-world example, building my own business website in twenty one hours. Unlike most AI influencer reels, which promise that you can do anything if you just follow and like, I'm going to tell you the cold hard truth. I'm also going to tell you what not to do, which these annoying reel-heads don't.

For twenty five years I have built websites for other people. I started coding at thirteen and shipped my first real mobile app in 2008. Most of my career since has gone to the back end and the full stack, the part nobody sees, the part that has to stay upright at three in the morning. I am also an inveterate battle-hardened sysadmin who can white-hat hack, can do things at the terminal prompt that you had no idea existed, and maybe that's why I am an extremely proficient AI engineer. I like to brag I can do more with a single text file than most people can do with ten laptops. Systems thinking, first principles, I was born for this AI stuff. Anyway, through most of that stretch, my own company had exactly one placeholder page on the internet. It went up so the business could enroll as an organization in Apple's developer program, and there it sat, dark template and all, for the better part of a year.

When I finally sat down to replace it, one line kept coming back to me, and I later used it to open the launch email. The carpenter with not a squeaky door, but no door at all, built himself a bank vault.

This one is public. If you build things, or pay someone to, send it along.

When AI had its breakout, across 2024 and 2025, the entire conversation was about AGI: the moment the machine wakes up, becomes conscious, and starts thinking like us. I do not believe in that moment, and I do not think the thing is anywhere near it. It's literally a computer program, folks. Set that ceiling aside, though, because there is a much lower bar sitting in plain sight, and the machine cannot clear that one either. Taste. The ability to look at two things that both work and say which one is better. Consciousness is the argument nobody can settle. Taste is the floor, and the machine is still underneath it.

This is the story of that build. More usefully, it is a story about what an AI coding assistant can and cannot do, told by a professional software engineer who leaned on one hard, for about twenty one hours straight, and watched it work in real time. The short version is the title. The longer version comes with a control group, and the control group is what makes it worth your time.

Carpenter With No Door

I am a systems person by trade, and I want that on the record before anyone grades my color choices. I find the problem a business has and does not yet know it has, and I fix the thing under the thing. Here is the part I undersold to myself for years. Before the code, I was an art kid. I dreamed of being a fashion designer or visual artist. I applied to art schools and got accepted, but Asian parenting put a stop to that nonsense. I became a professional photographer by accident anyway. My work hung at the United Nations and at state fairs, I was tracked into the gifted and talented art classes, and I kept an amateur design career running on the side long after. I will never be the Jony Ive of graphic design. I am something more ordinary and more useful here: a coder with a trained eye, someone who knows what good looks like and can see in half a second when something is off. Hold onto that, because it turns out to be the whole instrument this story is about, and it is the one faculty the AI does not have. So when I decided to build my own site, I faced the choice anyone without a design department now faces: hire someone, drag boxes around in a site builder, or sit down with an AI assistant and drive.

I drove. I fly through code like Tom Cruise in an F/A-18 Super Hornet single seater. Hand written HTML, one stylesheet, one script, no framework, nothing on the page I cannot read. The finished site is eleven pages, six hundred and sixty six lines of CSS (yes, the number of the beast) and three hundred and fifty three lines of JavaScript.[1] The only outside library is a 3D engine for one faint drawing behind the hero, and it loads on wide screens only. From a back end guy, that minimalism is a statement in itself. If I cannot read it, it does not ship. Loaded in the same browser on the same connection, my home page makes 13 network requests and weighs 252 KB. A former partner's site, built on one of the big hosted builders, makes 153 requests and weighs about 1.46 MB for less text and worse accessibility.[6] A back end person building their own front end has one unfair advantage: they know exactly how much of what the builders ship is unnecessary.

Most "I built this with AI" posts skip the next part, because all they have is the after. I can show you the before, since the only variable that changed between the two was me opening my mouth.

I Brought My Homework

I walked in with the homework already done and encoded into tools. Nobody can say I started from a blank prompt and found out halfway through that taste matters. I have a rating engine I built myself.[2] It loads a site in a real browser at three screen sizes, in light mode and dark, runs accessibility and performance checks, then hands the result to three separate AI judges that score forty seven criteria against written standards, plus a fourth agent whose entire job is to argue the scores down. I have design playbooks, every rule tied to a source. I even loaded the assistant with a published design skill that warns against the current tells of AI generated pages.

Put another way, I brought exactly what everyone tells you to bring. Research up front, references on hand, a rubric to keep the machine honest.

The first real pass took under half an hour. Out came a clean design language I ended up calling the bench: warm paper, graphite text, one green signal color, serif headings, hairline rules. It looked like a careful lab notebook. It was accessible. It was correct. The rating engine gave it an 86 out of 100.

And it was boring. A rubric gets you to competent. It cannot get you to yours.

I write about tech, media, and power, usually with more footnotes than this. Start a seven day free trial if you want the paid pieces too.

Plain Jane Changed Everything

Two rounds in, sitting at 86, I looked at the thing and typed this:

I'm thinking the design is a little plain Jane. My personality and intelligence is more lightning in a bottle, according to you.

Nothing in the rubric said "plain Jane." A rubric cannot feel plain. All it can check is whether the contrast ratio passes and the headings nest correctly, and both did. The dullness was real, and the score could not see any of it. I was the instrument that detected it.

So we built the loud idea. The hero became a dark panel in both themes, with a live electric line running through it that rings and crackles when your pointer crosses it, then settles and holds. A small gauge reads the load and reports that the system is holding. The headline is "systems that hold up under real load," and the interaction is that sentence acted out. One loud idea, taken literally, used exactly once on the page.

Then I asked for a faint 3D drawing behind the hero copy, the way diode.computer does it, and the entire brief was two words: not tacky.[3] That was the whole design spec, and it did the work. Just subtle adds, but careful ones, and actually I really believe the Michelangelo line about sculpting. It's not what you are taking away but judging if what remains is the final piece. So more about less is more later.

One number tells the real story. After the site got its personality, after the voltage and the 3D hero and the new pages, the rating went down, from 86.3 to 84.0.[4] Some of that was five pages being graded instead of two. The direction is the lesson all the…



This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit tatsuikeda.substack.com/subscribe