My GitHub bio says “90% AI. 10% Googling. 100% shipping.” It is a joke, and it is also true. AI writes a large share of the code in everything on this site. People have started calling that vibe coding. I think the label misses the part that matters, which is everything I do around the code.
What I actually decide
The assistant types fast. It does not know what is worth building. I decide the scope of a project, how it should behave, what “done” means and what is not ready to show anyone. When I built ClipDeez, a tool that turns long videos into short clips, I decided it would be one milestone at a time and that the portfolio would say plainly which parts exist and which are planned. Right now it is milestone 1 of 10.
The habits that make it trustworthy
- Tests that can fail. Lanternfall has 336 rule checks and a 44-step interface test. Mainspring has 966 checks and a 58-step test. ClipDeez’s back end has 263. I have caught real bugs this way, and I have also caught a test of mine that could never fail. A check that cannot fail is worse than none.
- Measure before fixing. When this portfolio felt jumpy on phones, I measured it first with a scripted browser, found the cause, fixed it, and measured again. The numbers are in another post.
- Look at the real thing. I open pages in a browser at phone widths and click everything. Code that reads correctly is not evidence that it works.
- Label what is not built. Previews say they are previews. Sample data says it is sample data. Planned features say they are planned.
- Keep secrets out. Before anything goes live I scan for keys and passwords, and I keep real client data out of anything public.
Where the 10% Googling goes
Mostly to reading how something really works before I trust a summary of it. When a number or a rule matters, I would rather check the source than accept a confident-sounding answer.
What I am honest about
I use AI heavily, and I say so on the front page. I also test things, and I keep a list of what I have not verified. If you are hiring someone to build something, I think that combination is the useful one: fast, and checked.
You can see the results on the Work section of the home page, with a full walkthrough for every project.