About

I'm Vadim, a Data Engineer at Addepto, a data consultancy based in Poland. Over the past 4+ years at Addepto, I've worked across chatbots, web apps, analytical platforms, and data engineering. For the last 15 months, I've been fully focused on Databricks, building a multi-modal transport data platform that integrates aviation, rail, and maritime data. Most of that time, I've been the only data engineer on the project, owning the full technical scope: architecture, development, backlog, and stakeholder communication.
I hold both the Databricks Data Engineer Professional and Associate certifications. I graduated #1 by GPA in Software Engineering at university. I've published technical articles, conducted workshops for engineering teams, and mentored a fellow data engineer from his first Databricks project to taking full ownership on his own.
Here's what drives this blog: when I started working with Databricks, the content I needed didn't exist. Tutorials explained concepts. Documentation described features. But the gap between "here's the idea" and "here's how to actually build it" was filled with guesswork. I spent hours configuring things by trial and error, making architectural decisions without confidence, not knowing whether my approach was right until something went sideways.
I decided to become the resource I wished I'd had. I document what I learn while building real Databricks systems: the patterns, the architecture decisions, the configuration details, and the lessons that tutorials leave out. Every blueprint comes from something I've actually built and used.
I'm not teaching from above. I'm documenting alongside. The climb is ongoing, and I'm sharing every step.
I originally moved from Ukraine to Poland at 19 to study software engineering. 918 kilometers from home, knowing nobody. That same "figure it out" mindset still drives how I approach engineering and writing.
Outside of work, I enjoy sports (yoga, calisthenics, tennis, skating — you name it) and love to cook — particularly cheesecakes. I won't claim they're the best, but they tend to disappear quickly 🍰
On AI in my writing
I use AI tools throughout my writing: research, analysis, drafting, all of it. What I share comes from my hands-on engineering experience: patterns I've applied, decisions I've wrestled with, lessons I've picked up along the way. The opinions and occasional cheesecake digressions are entirely mine.