Ekaterina Korolkoviene
I’m a data engineer who builds tools, systems, and platforms — and enjoys watching them come alive brick by brick. I started as a data analyst, fell in love with Python, and gradually shifted from thinking in tools to thinking in systems and outcomes. I care deeply about automation, observability, and how all the moving parts fit together. Most of what I’ve learned comes from building things in production, fixing what didn’t work, and understanding code beyond the surface.
Session
At some point, every Python developer hits a library that no longer fits. The docs end, the abstraction leaks, and you’re stuck between “best practices” and shipping.
This talk starts with a mistake: modifying a library’s source code and proudly posting about it. It worked - and it taught me a better way.
This isn’t a tool talk. It’s about mindset. Libraries aren’t sacred. They’re code. Code you can read, understand, and extend. And learning to look inside is a skill, not a sin.