I was doing my TryHackMe training this morning, working through the OWASP LLM Top 10 for 2025, when I hit LLM09:2025 — Misinformation. I thought I had this one covered with Sentinel, my AI security proxy. Misinformation detection, hallucination flagging — I'd mapped all of it. Then I went deeper and hit something I hadn't explicitly named: package hallucination. I'd seen it happen. I'd caught it m
The "open this URL on your phone" problem: your laptop is showing a deploy preview, your phone is on the desk, and copying-pasting a long URL between them is awkward. ascii-qr "https://..." prints a QR code right in the terminal — your phone scans it from across the desk, you're done. 150 lines of Rust, single static binary, works over SSH and inside CI containers. Here's the trick that makes the
Waymo Drives Off with South Bay Man's Luggage
Maybe recognition is less about detached labels than it is about where something is, what surrounds it, and how that context gets reinforced. That is what pushed me to build this repo. I wanted a smaller problem that still felt close to the thing I cared about. The question that kept pulling me back was whether location and context are a big part of knowing something at all, and whether they help
Introduction In Part 1, we successfully moved the resume from a local editor to a live URL. But an empty repository is like a house without a front door, functional, yet inaccessible to those looking in. In this second installment, we’re going back into the terminal to master the art of the README. I’ll show you how to turn a folder of code into a polished, technical portfolio that speaks for it
I do a bunch of small things on the side. I wrote a website for a friend's thesis, took on a couple of commissioned full-stack jobs, and I have one actual side hustle that's trying to make money. None of them live on the same stack. I keep picking whichever provider has the most generous free tier for that specific thing. The thesis site is on Firebase, the commissioned stuff is on another host, t
How I removed a legacy behavior that optimized for likability—and paid for it with self-respect. Context I recently ran an audit on a behavioral pattern I had been running for years: If (someone needs something) I thought this was a virtue. In practice, it behaved like an anti-pattern: It scaled poorly So I treated it like deprecated code and started a refactor. The Bug: Over-Availability as a Def
Git saves your history locally. On your machine. Invisible to everyone else. GitHub puts that history on the internet. Now your code is backed up off-site. Now collaborators can contribute. Now recruiters can see your work. Now you can open your project from any computer in the world with one command. GitHub is not just Git storage. It is your professional portfolio. Every project you build in thi