Hi, I’m Dee.

I work in cybersecurity — the part where you spend years building defences, and then watch someone click a phishing link anyway.

By day I think about risk, governance, incident response, and how to explain threat models to people who would rather be doing literally anything else. By night I build small things with AI, read source code nobody asked me to read, and occasionally post Kannada philosophy to Mastodon.

What this blog is

Three things, loosely held together:

Vibe Coding Projects — I’m building one thing a day with AI assistance for 100 days and writing honestly about what happened. Not tutorials. Not polished how-tos. Just: here’s what I tried to build, here’s what broke, here’s what I learned. Some projects took an afternoon. Some took until 2am. All of them shipped.

Curl Notes — curl has been running on virtually every computer since 1998 and I decided to actually read its source code. These are the notes. Slow going. Entirely self-inflicted.

Reading — Books, papers, and articles that changed how I think about something. Key takeaways, open questions, and connections to things I already knew.

The longer version

I’ve spent enough time in security to know that the scariest vulnerabilities aren’t in the code — they’re in the assumptions. The “this will never happen” and the “someone else is handling that” and the “we’ll fix it after the release.”

I started this blog because I wanted a place to think in public. Writing forces clarity. Shipping forces honesty. And doing it for 100 days in a row forces the kind of consistency that’s harder to maintain than it sounds.

The vibe coding series is my answer to a question I kept asking: what can these AI tools actually do when you give them a real problem and hold them accountable for the result? The answer, so far, is: more than I expected, differently than I expected, and never quite on the first try.

Find me elsewhere

No tracking. No newsletter. No “I’m building in public” LinkedIn posts. Just the blog.