Skip to main content
// why this exists

Ever met a 22-year-old software student who didn't have a GitHub account? (I'm still processing how that's possible.) Anyway — instead of just emailing him some notes, I did the most logical thing possible: I over-engineered a solution and built a whole website.

It was supposed to be a few quick notes. How to talk to AI, what to watch for, the stuff that actually matters. Then I realized there's a whole group of people who have the vision to build things but just need someone to translate the tools.

// who I am, briefly

A nerd. Computers since childhood. 300-ping bunnyhopping across Dust 1, 50-cent-a-text Nokias, the original MMOs and social media — I didn't just grow up with the tech, I watched the industries and laws form around it.

Professionally, I got lucky. I worked alongside engineers and architects who were way overqualified for their roles, and they taught me how to see systems. I can architect something in my head, understand the data flow, write the docs. I just don't write the code.

Systems are systems — from people to computers. You can work with what you don't fully understand if you know how to ask the right questions.

// who this is for

People who want to use AI as a tool to help them build. If you've got the drive to create something but felt sidelined because you aren't a "coder" — this is the bridge.

I don't know if this will work for you. But it's honest, and it's free. Thanks for looking.

// this is
+ notes from real projects and real mistakes
+ plain-english explanations of things that sound scary
+ honest about where AI struggles and where it shines
+ copy-paste prompts you can use right now
// this isn't
- a coding course
- a portfolio disguised as content
- sponsored reviews or affiliate marketing
- going to ask you to subscribe or sign up