Building Open Data Dictionary (Part 1)

🎃 Since it's Halloween, time to post something scary (probably for me).Scary in the sense that it’s something way out of my comfort zone and I’m sharing it publicly.So here it is...

I’ve been working for 13 years in the Data (and now AI) space, and there’s always been this itch I just couldn’t ignore.

That’s building my own app/website/product.

It’s been several months since I started tinkering with this project, and I think I’ve finally reached the point where I can share a bit of what I’ve been building and learning along the way. To give some more background, I’ve spent most of my career in Python, SQL, and three familiar letters: E, T, and L. Recently, I’ve been more focused on Engineering Management, so building a website or app again feels like a steep mountain to climb or run (if you are into trail running). The last website I built was my university thesis, a project called Roccus, named after a Striped Bass 🐟. (I still don't remember how I ended up with this name)

It was a Patient Health Record System with a poor man’s version of “AI”, a basic recommendation system that ranked possible diagnoses based on the symptoms you entered.

So... fast forward to today, after throwing away countless ideas, sketches, and “maybe this is it” moments, I think I’ve finally landed on a problem worth solving (more to that in the future).And thanks to GenAI and LLMs, there’s no better time to dive in and see what vibe coding really feels like.

That’s all I’ll share for now.Stay tuned for Part 2, where I’ll talk about my tech stack choices and how I ended up deciding on them.