7 Mistakes That Cost Me Hours Building Sites with AI (So They Won't Cost You)
The short version
Across building several live sites and an app as a non-technical beginner, I made the same kinds of mistakes everyone does — and each one cost me real hours. Here are the seven biggest, exactly what went wrong, and the simple fix for each. Read this and skip the pain I didn't.
The seven mistakes
I'm not a developer. Over a few weeks I built and launched several websites and a mobile app using AI tools as my guide. The building was the fun part. The mistakes were where I actually learned — and most of them cost me hours I'll never get back. So here they are, honestly, so they cost you minutes instead. Every one of these genuinely happened to me.
1 Pointing at the wrong nameservers
This is the one that nearly broke me. On one launch, I carefully entered every DNS record correctly — and the site still showed a "parking page" for hours. At one point it even displayed a message suggesting the domain had expired, which sent me into a small panic. I'd just paid for it.
The domain hadn't expired at all. The problem was a layer above the records: my domain's nameservers were pointing at the registrar's parking service instead of its real DNS service. So all my perfectly-entered records were sitting in a directory that nothing was consulting. They were being completely ignored.
2 Pushing code I hadn't tested
On my word-game project, I got excited, made changes, and pushed them straight to the live site without checking them first. The deploy failed. So I tweaked and pushed again. It failed again. Four times in a row. Each failure cost time and a little more confidence, and the cause was always the same: I was publishing changes I hadn't actually run myself first. One of them referenced a file I'd forgotten to include.
3 Trusting the browser cache (and seeing ghosts)
This one made me feel like I was losing my mind. I'd deploy a fix, the platform would confirm it was live, I'd reload the page — and the old behaviour would still be there. I'd assume my fix hadn't worked and start "fixing" something that was already fixed, making things worse.
The culprit was browser cache: my browser was showing me a saved older copy of the page instead of fetching the new one. The fix was live; I just couldn't see it.
4 Believing the AI when it was confidently wrong
I love AI tools — they made all of this possible. But I learned the hard way that they can be confidently, completely wrong. The worst saga was getting my word game to accept only real words. The AI's solutions sounded authoritative each time, yet one approach accepted obvious gibberish, another rejected perfectly real words, and it took round after round to get right. A separate tool once kept inserting the wrong year into dates because it was guessing rather than checking.
The pattern: the AI's confidence had no relationship to its correctness. A wrong answer was delivered just as assuredly as a right one.
5 Putting fake numbers on the site
When my sites were brand new, the design templates came with impressive-looking placeholder stats — "thousands of users," big visitor counts. On more than one site I left them in at first, thinking they made me look established. That was a mistake on two fronts: it's dishonest, and ad networks and search engines actively dislike sites making claims that obviously aren't true. Visitors can sense it too.
6 Nearly exposing secrets that should stay hidden
Some of my projects needed secret keys — credentials that let my site talk to a paid service. The dangerous beginner instinct is to drop those keys straight into the website's code, where anyone viewing the page could find them. On the projects that needed them, I learned to keep keys on the server side only, hidden from the browser entirely, so visitors never see them.
7 Panicking instead of waiting
My most expensive mistake wasn't technical — it was emotional. Several times, something looked broken when it was actually just slow. A new domain not showing up (DNS still spreading worldwide). A change not appearing (cache). My instinct was to assume disaster and start frantically changing things — which sometimes broke what was quietly working fine.
The irony: one time my gut told me something was genuinely wrong (a setup taking far too long), and I was right — that was the nameserver issue. The skill is telling the two apart, and you only get there by slowing down.
The bottom line
None of these mistakes meant I'd failed — they're the actual curriculum of learning to build things. But every one cost me time you don't have to spend. If you remember just three: check your nameservers when DNS misbehaves, never publish untested changes, and don't trust the AI (or your own panic) without verifying. Do that, and you'll skip most of the hours I lost. Breaking things is part of building. Breaking them the same way I did is optional.