Real John here, this week has been a bit crazy for me, but all in all a good week. Doing some interviews, getting some Street Fighter time in, and of course my new Puppy life is work. The highlight of this week: I got feedback on an open-source project… something I thought was simple, but a walk-through was the request. Here’s the result of what actually happened.
This week is kind of short, but here’s what I’m at. Also don’t forget to follow my Not-So-Daily live stream on youtube.
I built a VS Code extension to answer one question: how much Codex usage do I have left?
It puts the answer in the status bar. That’s it. No extra dashboard. Just enough information to decide whether to start a bigger task before the limit resets.
The extension has a GitHub release. The README explains how to install it. And then I got a useful piece of feedback: make a quick-start walkthrough.
It’s tempting to point at the README and call it done. The steps are there. That’s not the same as giving someone a good first run.
The question wasn’t whether I’d written down the steps. It was whether someone who’d never seen the extension could get to the part that made it useful.
Installed isn’t the same as useful
On my machine, I know which file to download. I know the official Codex extension needs to be installed and signed in. I know where to look once the tracker is running.
A new user sees a file ending in .vsix. Maybe they know what to do with it. Maybe they double-click it and wonder why they now have a very small, very unhelpful file on their desktop.
Even if installation goes fine, they can still miss the payoff. The thing I built is a tiny readout at the bottom of an editor full of tiny readouts. If I don’t tell you where to look, you can install the extension correctly and still think it didn’t work.
So the walkthrough I want starts with the destination: look at the bottom of VS Code. You should see how much of your Codex limit you’ve used. Then it works backward. Here’s the file. Here’s how to install it. Here’s what needs to be signed in. Here’s what to check if nothing shows up.
That’s a different job from explaining how I built it. Nobody downloaded this thing to hear about my packaging decisions. I barely want to hear about my packaging decisions.
Watch one person try it
If you just shipped something with AI, this is where I’d spend the next half hour. Not adding another feature. Not asking AI to make the README sound more exciting. Put the release in front of one person who wasn’t there when you built it.
Give them the link you actually send people and ask them to show you the first useful result. Then stop talking.
Write down the first place they hesitate. Not the fifth. Fix the first one and give it to someone else. For my extension, that might be a clearer download link, a screenshot of the status bar, or putting the sign-in requirement before the install command. Which one? I won’t know until I watch someone try it.
AI can help turn those notes into better instructions. It can’t tell me what a real person missed if I never watched one use the thing.
The test I care about isn’t whether someone can follow my demo. It’s whether they can get the result after I leave the room.
Work with me
If you’re building something useful and want help getting it into people’s hands, get in touch at Startups & Code.



