Why this blog?
Technology changes. Curiosity doesn't.
Most technical blogs start with answers.
This one starts with questions.
Most of the software you'll find here exists for one simple reason: I wanted to know if it could be built.
For as long as I can remember, I've had the habit of taking systems apart. Not because I wanted to break them, but because I wanted to understand them. Sometimes that means reading specifications. Sometimes it means writing a quick proof of concept. Sometimes it means diving into source code until a tiny detail finally clicks.
Recently I noticed the same instinct in my toddler.
Give him a pile of plastic bricks and the first thing he does is pull them apart. Then, every time two bricks finally click together, he lifts them with a huge smile and proudly shouts:
"TADAA!"
Watching him made me realize that's exactly how engineering often feels.
We dismantle complex systems into smaller pieces. We inspect every component. We make mistakes. We rebuild. Eventually, two ideas connect, and suddenly something that looked like magic becomes understandable.
That little TADAA! moment is addictive.
This blog is a collection of those moments.
By day and by night
By day I build software for mobile security. I spend a good amount of time around authentication, SDKs, fraud prevention, and all those systems that, when they work well, nobody notices.
This blog is about everything that happens outside that day job.
It exists because I enjoy building things. Sometimes they're useful. Sometimes they're ridiculously over-engineered. Occasionally they're both.
Most of them begin with a single question:
"I wonder if…"
That question alone has probably been responsible for most of my side projects. Not because someone asked me to build them. Not because there was a business opportunity. Simply because I wanted to know whether an idea could become reality.
There is something deeply satisfying about taking an abstract idea, turning it into a design, writing the code, watching it fail a few times, improving it, and eventually seeing it come to life.
The toddler has his plastic bricks. I have Swift, Kotlin, and Go. The feeling when something finally clicks is not that different.
What you'll find here
There isn't a single topic.
Some articles will be about authentication, mobile engineering, behavioural biometrics, SDK design, RASP, reverse engineering, distributed systems, AI, networking, compilers, or whatever has captured my attention lately.
What ties these posts together is the process more than the stack.
I want to document how ideas evolve, how prototypes fail, what surprised me, and what I learned while trying to answer a seemingly simple question. Every article should leave you with at least one new idea, even if you never copy a single line.
Expect code.
Expect experiments.
Expect diagrams.
Expect the occasional dead end.
Above all, expect curiosity.
You'll also occasionally find references to pizza, lack of sleep, movies, TV shows, and life with a tiny human who recently became my favourite debugging companion. Engineering and real life are allowed to coexist on the same page.
A journal, not a showcase
There are already countless blogs explaining how to use a framework, copy a library, or paste code from Stack Overflow.
This probably won't be one of them.
I'm not aiming for a tutorial site, a portfolio, or a résumé with nicer fonts. I'd like a journal where ideas become software, and where the story behind the code gets as much room as the code itself.
I'm not trying to become an influencer. I'd like to leave behind an engineering narrative. Years from now, if someone reads a handful of these posts, I hope they understand not only what I built, but how I tend to think about problems.
Some threads will stay loose notes. Others might grow into series. No fixed roadmap, no release schedule. If a topic goes quiet, I'm probably stuck on something worth getting right before I publish half of it.
If an article makes you pause and think, "that's an interesting idea", or leaves you wanting to try something yourself, it has done its job.
Welcome aboard.