Skip to content
Personal essay·Security·3 min read·Sep 12, 2026

Just Enough Security

A small, real example of dumb, cheap security — and why it was enough.

Last essay was about what “software engineer” should mean now that code got cheap. Security got one paragraph in it. That felt too short, so here's the longer version.

Since we're already on the topic, let's talk about dumb security — or how to protect yourself from spam without overkill, on one simple example.

The green light

When I built the contact form on this portfolio, an LLM and I worked on it together until it ran. It looked right, it worked, and the LLM gave me the green light: ship it. We even added CORS, which felt like a safety measure at the time. It isn't, really — CORS is something a browser enforces. Something like curl doesn't care about it at all.

What I missed

It took me a bit longer to notice the actual problem: the route itself was wide open. Anyone could spam it, any time, with anything. The LLM never flagged that, and I don't think it was being careless. It just doesn't understand the greed and hypocrisy in human nature the way someone who has actually dealt with spam does. It only builds to the standards already floating around the internet. Nobody had written down “expect a stranger to abuse this,” so it never came up.

The fix

So I decided to fix it — and why not fix it with the help of that same LLM. I won't explain how, exactly; we're not talking about prompt engineering today. From the simple stuff, the kind you can build in literally a day, we made this: a hidden honeypot field, a check on how fast the form gets filled out, a small scoring system that combines several weak signals instead of trusting one, a rate limit per IP, and a proxy that hides the real webhook address and its secret key from the browser. A dropped submission still gets told “success,” so nothing about it looks different from the outside.

Enough

In my opinion, that's enough. This is a contact form on the portfolio of one software engineer nobody needs. Worst case, I'll have their IP, and it's far more likely to be someone I actually know than some random stranger on the other side of the planet who has nothing better to do than DDoS a nobody's portfolio.

So why tell this whole story? Since “software engineer” isn't just someone who writes code anymore — though writing secure code was always required — you have to think through questions like this one too. Whatever goes to production under your name, yours or someone else's if you're the one doing DevOps, you need to be as ready as possible for anything. The LLM won't do that part for you. Audit your own workflow.

Mr. Keating told his students to find their own voice, not somebody else's, and to make their lives extraordinary. Carpe diem. I'd add one thing to that: think it through yourself first. The model won't do that part for you either.

Comments
  • Be the first to comment.