Profile avatar
ivanovyordan.com
Enroll on my FREE data engineering course: https://datagibberish.com/p/free-data-engineering-course?utm_source=bluesky&utm_medium=social&utm_campaign=about&utm_content=enroll-my-free-data-engineering-course
162 posts 161 followers 180 following
Regular Contributor
Active Commenter

Data engineering is a thankless job. That's why it feels so special when you hear that "thank you" from a business stakeholder, you rarely talk to.

How amateurs code ❌ Optimising "just in case" ❌ Writing bespoke pipelines ❌ Building projects in one go How the pros do it ✅ Optimising actual bottlenecks ✅ Crafting reusable components ✅ Iterating over MVPs

As a Head of Data Engineering I reject candidates for 3 reasons: 1/ Toxic culture Don’t talk trash about people or code. 2/ Shallow technical understanding Read books and docs. Write code. Debug. 3/ Poor communication Ask for feedback. Notice follow-up questions. Work on these.

Top 3 resources for beginner data engineers (unordered) 1. Fundamentals of Data Engineering (bit.ly/41g1ITU) 2. 100 Days Of Data Engineering (bit.ly/3X4FOjV) 3. Data Engineering Zoomcamp (bit.ly/3X69XiV) Bonus: My SpaceX Missions email course (bit.ly/3D6lxDE) These will save you 100s of hours.

The best way to become a better programmer is to build more. The best way to become a better analyst is to explore more. The best way to become a better leader is to inspire more. Stop overcomplicating it. Just do more.

Most companies fail with them. A data driven decision requires effort: A ton of planning. Even more collaboration. Most people look for shortcuts. There's no success without effort.

I used to struggle to connect with stakeholders. Today I build strong relationships with them. Trust me: It gets easier. Each group speaks a different language. The key is to tailor your message to them.

It's okay to neglect code quality to provide business value quickly. But don't forget to set time aside to pay your debt.

The early years of your career are painful. Long hours Mediocre pay Minimal vacation days Don’t worry though. It gets way better. Here are 4 career shortcuts to get you to “the good life”. ⤵️

Bad Data Engineers 1/ Trust the docs 2/ Focus on the solution 3/ Dream of learning everything Good Data Engineers 1/ Read the code 2/ Focus on the value 3/ Learn a couple of tools deeply Is that fair?

Data Lakes For Complete Noobs: What They Are and Why The Hell You Need Them datagibberish.com/p/what-are-d...

You jump into a new big project. Here’s how you learn it quickly and provide value early: 1/ Load the project in VS Code 2/ Pop open Github Copilot 3/ Use thie prompt:

3 reasons you should follow me (and thank yourself later) I show you what works (and what fails). I know the pain of debugging at 2 AM (and hate it). I fix broken ETL faster than a tractor (it's still in my yard). If you are in reach out if you are in Data, tech or startups. I'd love to connect!

Your code is rubbish. Most data data engineers write terrible code. It’s unscalable, hard to read, and impossible to debug. Not to mention data science code. The market is extremely hard nowadays. You can’t be like everybody else if you want to shine. You need to write readable code. ⤵️

Here’s an unpopular opinion: Buying tools fast slows you down. Most people think speed is everything: Grab the latest tool, sign the contract, and go. But here’s why I disagree: Rushed decisions lead to wasted money and endless migrations. ⤵️

Scarecrow: I haven't got a brain... only straw. Dorothy: How can you talk if you haven't got a brain? Scarecrow: I don't know... But some people without brains do an awful lot of talking... don't they? — L. Frank Baum Leaders Good leaders know this. ⤵️

I spent weeks on a project to achieve nothing and throw it away. The goal was to see how users use a feature and if we need to invest more into it. Instead of doing just that, I focused on: Perfecting data quality Automations Scalability

Don't prioritise data quality Prioritise business value. A few minutes. This is how much you need to scroll LinkedIn to find a post on how you must take care of data quality before you even move your finger for your stakeholders. I disagree. ⤵️

Don't prioritise data quality Prioritise business value.

Are you upset by DeepSeek? Winners are finding ways to profit. Here’s their secret: They offload low-leverage tasks to AI. I like writing documentation, but I LOVE coding and talking to people. One task I offloaded to DeepSeek was generating scoping docs. Here's how you can do it too: ⤵️

datagibberish.com/p/comparing-...

Check my article. It's live, now.

The best way to increase job security is to work less. I used to work 10+ hours a day. 7 days a week. Nobody asked this from me. I felt obligated to do it. In a team of one, you manage your projects end to end. Every failure and every new request is your responsibility. ⤵️