About Me

· 2 min read

I’m a professional data engineer living in Vienna, Austria, working for Magenta Telekom as a Data Platform Engineer.

Here you can find a list of tools, frameworks, and resources with reasoning for why I like and use them as a professional data engineer.

Learning Resources

CMU Database Group

YouTube channel from Professor Andy Pavlo. This is the first course that actually helped me in my day-to-day job as a data engineer. I would recommend first watching Intro to Databases, then the Advanced Database course, and finally all the seminars and guest lectures for the latest information and system understanding. There is a lot of material—I’ve been following it since 2021. I recommend starting with the new semester and watching videos as they’re released.

Gilbert Strang’s Linear Algebra

This changed my mind about teaching and learning math and was a point where I understood why we need math to solve real problems. He teaches very simply, almost making you feel like you’re figuring it out together.

Frameworks and Tools I Use Every Day

Dagster

Data orchestration platform - Dagster changed the way of modeling data flow from task-centric towards a more natural asset-centric approach.

dbt

Data transformation tool

BigQuery

Google’s data warehouse - I like that their pricing model pushes you to think about the most important part of working with data and this is how to early prune as much data as possible.

GitLab

DevOps platform

Claude

AI assistant by Anthropic

Things I’m Interested In But Not Using Day to Day Yet

DuckDB

Embeddable analytical database - First of its kind to bring the depths of analytical databases into a single process. A great community and great things are ahead for DuckDB.

DuckLake

Open data lake and catalog format - It’s a great idea to converge toward known patterns while addressing modern needs. I feel really excited about the future of the project.

Rust

Systems programming language - No pointers going to nirvana (my professor at university’s quote) due to very simple compiler rules forcing you to define who is responsible for working with a memory block.

Attributions