Writing
Field notes
Plain-language guides from things I've actually built with AI — what mattered, and why.
I spent 577 credits teaching an AI to spin a can. Then I built the can.
I burned 577 credits trying to get an AI to show the same can from every side. It never managed it once — and that's not bad luck, it's how these tools work. The fix took one sentence, no special skills, and it changed how I use AI images entirely.
I turned my résumé into an escape room — the game got good when I cut the résumé
I pitched my AI an escape room where reading my résumé is how you get out. Thirty-three prompts later, a stolen-diamond noir leads my site's arcade — and the résumé is gone. I never wrote a line of code. What I did instead turned out to be the actual job.
I put an app on my home screen in a day — here are the six prompts
I built a to-do app and put it on my phone's home screen in a day — six prompts, start to finish. The surprising part wasn't that it worked. It's how loose the prompts were: typos, half-sentences, one that's just "what next?" — and that three of the six could be that sloppy because a system I'd built before the project carried the quality the words left out.
I built my friend's food truck a full ordering system. I shipped the simple version.
I built a full online-ordering system with Square payments for my friend Robert’s food truck — and then shipped something much simpler. The real skill wasn’t building the impressive version. It was knowing what not to ship.