There's a lot of confusing advice about AI. I'm trying to boil it down.
Most of it is either too basic to be useful or written for people who already code. What I want is the middle: how a person actually starts using this, first steps and beyond, without it being overwhelming.
So I build things and write down how it really went, and I try to teach the first steps in plain language.
I've spent my career in business operations and HR, not engineering. That's the point. If I can work it out, so can the person in the next office.
I do this from 4:00am to 6:00am, a few days a week, before work starts.
WHAT'S HERE
AI at Work
Five sentences you already say at work, and how each one works on an AI. Written for someone who has never opened one of these. What I’m working on in it now is the first step, so a beginner actually tries something instead of reading about trying it.
Builds
Every project so far, each one with the raw log of how it actually went: the walls, the dead ends, what carried into the next build. The one I’m in the middle of is a test of three AI models on the same real task, graded.
Kid Lab
Robot athletics, designed by my son. He has final say on everything in there. Basketball, the warped wall, and boxing all work. Soccer just went in, with a goalkeeper who dives.
The Lab
A 3D experiment: the builds orbiting in a starfield, with a sunrise you drive by scrolling. It’s where I try interface ideas that don’t belong on a normal page yet.
THE BUILD STORIES
I don't just post what worked. Every build includes the walls, the dead ends, and the thing that survived into the next one, written from the timestamped records.