Solving real problems first
Because I worked in IT support and live operations, I’m used to real people with real problems:
“The school network is down”, “The event is starting in 5 minutes”, or “The system is stuck”.
That experience influences everything I build. I think about how someone will actually use it,
what breaks in production, and how to communicate fixes in a way that normal people understand.
Building full journeys, not just pages
I like building systems end-to-end: UX, front-end, backend logic, hosting, analytics,
and the content or documentation on top. A good project for me is something that
doesn’t just look clean – it actually works better than what existed before.
That can be a corporate site, a supplier portal, or a tutorial that finally shows
every step of a complicated game fix.
Using AI as a collaborator
For the last ~3 years I’ve been using AI as part of my daily workflow – to draft code, refactor,
generate variations, and brainstorm. But I always keep control over the final architecture,
details, and testing.
I see AI like a very fast teammate that needs clear instructions and constraints.
If you give it garbage, you get garbage. If you build the right structure, it saves hours.