I like building things. All sorts of things, actually.
For a long time, software was my favorite playground. Give me an idea, a problem, or something that doesn't exist yet, and I'll probably try to build it.
These days, my curiosity has taken me well beyond code. Turns out, making things is addictive, whether it's software, hardware, perfume, or something completely random I decided to figure out at 2 AM.
-
L2 Technical Support Engineer at Laravel — I help developers and companies figure out why things aren't working (and occasionally why they are working). Mostly around Laravel Forge, Laravel Cloud, and the wonderful world of deploying applications.
-
Building Vetrol — Working on fleet management and vehicle technology. Basically, making vehicles a little smarter and businesses a little less dependent on spreadsheets.
-
Making perfumes at Iroza — Yep, actual perfumes. Fragrances, bottles, mixing things, the whole deal. Not exactly what you'd expect on a developer's GitHub profile, but here we are. 🧪
We don't talk about that anymore. 🤫
Languages? Frameworks? Tools? I've used a bunch, and I'll probably use a bunch more.
With AI changing how we build software, I'm less interested in collecting programming languages like Pokémon cards.
What matters to me is understanding how things work, why they work, what to build, and when to use (or avoid) a particular tool.
The best tech stack? The one that solves the problem without creating five new ones.
And yes, I still have my favorites. I'm just not starting a framework war today.
I'm not really a building in public kind of person.
Most of what I build lives in private repositories, client projects, or somewhere far away from GitHub stars and contribution graphs.
So if my GitHub looks a little quiet, don't worry.
I'm probably building something. Or making perfume. Or breaking something to figure out how it works. 😄