The story I told across the last twenty-one posts ended with twenty-two tools running at my hospital.

This post is what happened next. Tool number twenty-three is the thing you’re looking at.

Why a blog, of all things

When the story was finished, I wanted it to travel farther than my own building. So I did the thing that would have sounded absurd to me two years ago: I bought a domain and built a website. Myself.

The domain cost $10.45 a year — about two cups of coffee. Registering it took ten minutes. A person who once didn’t know what code was now owns a corner of the internet, and the entry fee was pocket change. That fact alone still feels strange to type.

The site itself is a static site builder called Astro, hosted on Cloudflare — the same Cloudflare from the story, just wearing a different hat. One command builds everything; a push publishes it. Twenty-one posts went up. A newsletter box went in. So far, nothing here would surprise anyone who read the tool list.

Then I wanted a comment box, and it got interesting.

The comment box problem

The ready-made options all had the same flaw. The popular ones require readers to log in with a developer account — fine for developers, exactly wrong for the people this blog is for, the ones who were told they couldn’t code. The other kind is a free widget that pays for itself with ads and tracking. I didn’t want either.

What I actually wanted was the way old Korean forums did it: pick any nickname, type any password, say your piece. No account. No permission needed. It turns out almost nobody offers that as a service anymore.

And there it was again, the question that starts everything: is there really no other way?

So I built it.

What building it actually looked like

In roughly a day, this blog got: a small database, a tiny program running on Cloudflare’s edge that receives and serves comments, a captcha so the spam bots stay outside, an email that lands in my inbox the moment anyone comments, emoji reactions, replies, edit and delete by password — and a hidden admin page where I can see everything at once.

I still don’t hand-write code. The process was the same loop as always: describe the behavior in plain words, let the AI write it, test it, tell it exactly what broke, repeat.

And in the spirit of honesty this blog runs on, the missteps were included, as usual:

• I first installed a ready-made comment system, shipped it, and only then noticed it forced readers to log in. It was live for about an hour before I tore it out and started over. Shipping the wrong thing taught me what the right thing was — a paid lesson, not a loss.
• Twice I deployed changes, saw nothing update, and briefly panicked. The culprit both times: a cache serving the old page. The fix was to wait. The real lesson was to stop assuming I’d broken something.
• My emoji reactions “didn’t work” in testing — until it turned out the tool was fine and my terminal was mangling the emoji before they ever left my machine. The bug is usually somewhere dumber than you think.

None of this required becoming a developer first. It required describing what I wanted, refusing the first “can’t be done,” and testing like a suspicious customer.

What this actually means

Here is the part I keep coming back to. A working comment system — database, server, spam protection, notifications — used to be the kind of thing you hired someone for, or did without.

The distance between “I wish this existed” and “it exists” has gotten so short that the only meaningful cost left is deciding to start.

That was true for a parking-lot lookup tool at a hospital in Korea, and it’s true for the page you’re reading. Same person, same method, no credentials acquired in between.

The demo is right below

So here’s the ending this post was always going to have.

The comment box under this article is tool twenty-three, or at least its newest part. No login. Any nickname, any password, and a captcha the bots can’t pass. Type “hi” and hit post — that’s enough.

When you do, an email will land in my inbox within seconds, because I wired that too, without knowing how to code, in an afternoon.

Go ahead. Leave the proof.

Comments

Loading comments…

Post Comment