I work with why. Always.

I started learning web development at the end of 2022. No bootcamp, no classroom, no connections, no head start. Structured roadmaps, YouTube, documentation, and building real things until they worked — while managing a full university degree at the same time. That combination is probably where my systems thinking comes from.

I don’t build things because they’re trending. I build them because the problem is real and I couldn’t find the right solution anywhere else. That’s why checkemaildelivery.com exists. That’s why WP Tools exists. That’s why I spent three weeks researching and writing a proposal for an intern management system nobody asked me to build — and then watched the team actually use it.

My approach has always been: diagnose the system before you touch the code. Find where it’s broken. Write the SOP. Get buy-in. Then build. This is not perfectionism — it’s how you avoid rework, surprises, and systems that only work because you’re maintaining them.

I’m building toward work that compounds — products, systems, teams. Right now I’m Team Lead at Glowlogix, working on an internal HR SaaS product, running a freelance practice, and shipping free tools for the community. I write about all of it because the thinking behind the work is more useful than the work itself.