I'm not an expert. I'm 53, I work in a warehouse during the day, and at night I build small JavaScript projects: a 2D game engine, a debugging HUD called BeeLadybug, and a little HTML5 games portal.

They are small projects. But I care about them a lot.

My little method: docs = bug hunting

I found a method that works for me. I write the documentation of my own projects, and I publish it on my site.

While I write, I read the code. Then I read it again. And again. When I have to explain a module in plain words, I suddenly see the strange parts: a method that does too much, a default that makes no sense, a case nobody tested.

So the docs and the bug fixing grow together. Every page I write is also a small code review.

Where AI helps me

I'll be honest: I use AI a lot. It helps me understand code, write prompts for my editor, fix bugs, and polish my English (yes, this post too).

Without it, I would be much slower. I'm grateful for that.

Where AI goes wrong with me

But there is one thing that makes me crazy.

For months I have explained to different AI assistants that my projects are open source. They are on GitHub. I publish them on npm. They are made for other developers, not for me.

And still, again and again, the answer starts from the idea that these are "personal" projects. Little toys for myself.

Why? I think the reasoning is something like: one person, no team, no company, no millions… so it must be a hobby for himself.

That hurts a bit. Being alone doesn't mean building alone for myself.

A real example: the CanvasAdapter and the DOM

Tonight I was testing the Chrome extension version of BeeLadybug.

  • On normal websites, the DOM and CSS part works great. On a real games site it found a distorted image, a slider overflowing the viewport and a trapped z-index. Real bugs, on a site that is not mine.
  • On canvas games, the HUD said: CanvasAdapter attached (0 entities). A canvas is just pixels. The browser doesn't know where the player or the enemy is, only the game knows. So from outside, the extension can't draw hitboxes unless the game shares its entities.
  • And I found a real bug: BeeLadybug draws its overlays on its own <canvas> elements. If a page has a rule like canvas { background: green; }, my transparent overlay becomes a green wall that covers the game.

That bug only appears on other people's pages, with other people's CSS. If BeeLadybug were just for me, I would never have found it. That is exactly why "it's open source, for others" matters.

So… trust AI or not?

My answer today:

  • Trust it to explain, to suggest, to speed you up.
  • Don't trust it blindly. Test everything yourself. Read the code again. Ask "why?".
  • Correct it when it makes wrong assumptions about you and your work. Again and again, if needed.

AI doesn't know your story. You do.

My projects are small, and maybe my code is not perfect. But they are public, they are free, and they are made for you.

If you want to try BeeLadybug and break it on your own site, I'd love that. That's how it gets better. 🐞💚