I’m 31 years old, a junior developer, and someone who decided to completely rebuild his career from scratch.
Not because it was easy. Not because it was obvious.
But because something in me felt unfinished — like I wasn’t yet building the things I was meant to build.
For the last few years, I’ve been learning how to code seriously. And if there’s one thing I’ve understood, it’s this:
Learning software engineering is not a straight line.
It’s a loop.
A loop of confusion → clarity → confusion again.
Every time I think I’ve “got” something, I discover a deeper layer underneath — runtimes, memory models, async systems, networking, AI tooling…
It’s endless. And at the same time: it’s fascinating.
This blog is my way of making sense of that journey.
Learning in public changes everything
I used to learn alone — reading, watching courses, coding quietly.
But staying in my own head slowed me down.
I understood things “well enough”… until I had to explain them, or until something broke.
Writing forces clarity.
It exposes what I thought I knew, and what I actually don’t.
This blog is not here to teach “from the top”.
It’s here to learn from the middle — from the messy path between junior and engineer.
I’m writing for people who are like me:
self-taught or reconverted
curious but overwhelmed
trying to understand not just how code works, but why
If that’s you, welcome.
The Learning Machine is not AI — it’s the human learning loop
The name came easily.
People talk a lot about machines learning.
But we humans also learn like machines: through iteration, feedback, and constant adjustment.
I’m not an expert.
I’m not pretending to be.
I’m transforming — and this blog is the engine of that transformation.
Learning to build software, one concept at a time.
That’s the philosophy.
What you’ll find here
1. Concepts I finally understand
From the event loop to runtimes, from API design to concurrency — explained the moment they finally “click”.
2. What I break (and how I fix it)
Debugging stories, mistakes, and the reasoning that got me out of them.
3. How I use AI to learn without becoming dependent
AI is my co-pilot, not my shortcut.
I’ll document the balance.
4. Notes on switching career at 31
The emotional, cognitive, and practical side of starting over.
5. My builds, failures, and shipping attempts
Because the only way to really learn is to ship things that barely work, then make them work.
What’s next
This is the first entry.
Next week, I’ll start a series on system design!
“Understanding system design for real” —
Coding the big architecture patterns from scratch.
If you want to follow the journey, you can subscribe — or just come back whenever you’re stuck, confused, or learning something new.
The Learning Machine has started.
Let’s see where it goes!