Jonas Forshell

Experienced Product Owner

2026-05-07

Why I keep building things with AI

A note on using AI to build real tools, learn through the details, and stay honest about what it does and does not make me.

aiproductuxlearning

I keep building small things with AI because it helps me think.

That is probably the simplest way to say it.

The Resume Builder is the best example, because I actually use it. The website and CRM taught me things too, but the Resume Builder gives me real value right now. It helps me work with my own applications, my own resume structure, and the kind of templates I actually like.

It is not perfect. It is not some polished product with a full team behind it. But it works. And I still think that is kind of amazing.

I am not doing this because I think it makes me an engineer. It does not. I learn small technical things here and there, but I am still not the person who should architect a real production system.

What I do learn is more around product work.

I notice flows more. I notice when copy is inconsistent, when things move around, when a button is unclear, when something takes too many clicks, or when the interface technically works but still feels annoying. I have always noticed small details like that, but building things makes me notice them more.

The UX and UI part is often the hardest. Not always for me directly, but for the way I work with Codex. If I give lazy prompts, or if I do not know the right design language, the result can be rough. It might function, but still feel off.

That is one reason I have started trying design tools alongside Codex. I want better starting points. Better examples. Better words for what I mean. If I can be clearer about the design and the flow, I think the output gets better too.

That also connects to how I want to work with developers.

I do not think this makes me much more technical. Not in a big dramatic way. But I do think it can make me clearer. If I have already thought through the flow, the edge cases, the awkward parts, and what "good" might look like, then I can probably write better specs and create less confusion.

At least that is the hope.

There is also a downside. I can spend too much time on small things. I can keep iterating because something does not feel right, even when it is probably good enough. Some of that is care. Some of it is probably confidence. I know that about myself.

But I still think it is worth doing.

It keeps me learning. It keeps my brain active. It gives me real feedback instead of just ideas in my head. And sometimes it is just cool to build something, use it, and realise that it actually helps.