❓ A little context
Some months ago, I started a side project called HexAPI Generator, a simple Python app that helps generate clean, hexagonal Java APIs.
At first, it was just a personal experiment: I wanted to make something that followed all the Clean Architecture principles I was learning in my Master’s program.
Nothing crazy.
Just a nerdy idea built out of curiosity (and too many late nights).
🎓 The unexpected twist
Fast forward to last week.
My former Software Architecture & Clean Code professor, the one who literally taught me these concepts, reached out to me.
He asked if he could use HexAPI Generator in his class to show his students how clean code and structure can come together in practice.
Yes… my own prof. Using my tool.
In front of the next Master’s cohort. 😳
⚖️ Mixed feelings
I was honestly shocked.
My first thought was:
“Wait… but it’s not even that polished. It’s full of small hacks and quick fixes!”
But he told me it was exactly the kind of pragmatic and well-structured code he wanted to show. That hit different.
It made me realize that sometimes, what we see as “unfinished” or “not good enough” might already be valuable to others.
🚀 What I’m taking from it
This small moment gave me a real boost of confidence.
I’ve been deep into Clean Architecture, DDD, and code craftsmanship lately, not just for the sake of it, but because I truly love when software feels right.
Hearing that my work could help others learn that too…
Yeah, that’s the kind of validation that keeps me going.
💭 The takeaway
We often underestimate our own work because we compare it to some “perfect” version in our head. But done > perfect, especially when done with care and intention.
So if you’re building something, even messy, even unfinished, keep at it.
You never know who might find it useful, inspiring… or even worth teaching.
Top comments (0)