Yordan Ivanov

All issues

The $0 → $1k data stack, the portfolio mistake most people make, and one LinkedIn post that blew up

My weekly recap with 2 new pieces + 1 viral post. Real talk, zero fluff, 3 quick links.

Hey friends,


This week, I wrote two pieces I wish I had read 5 years ago. And apparently I’m not the only one. One of them sparked a wild comment thread on LinkedIn. More on that in a sec.

Let’s dive in.


How to build a data engineering portfolio that actually gets you hired

Most portfolios are just a messy pile of projects. This one shows you how to tell a story.


image


Why I wrote it: Because no one tells data people how to make their work look good.


I break down the mistake everyone makes, and what to do instead.

Think: less GitHub graveyard, more “holy shit I want to hire this person.”


Read it here: Building a Data Engineering Portfolio



The simple analytics stack for speed, clarity & control

The stack I wish I had when I was drowning in data chaos.


image


Why I wrote it: Because everyone loves shiny tools.

But what we need is to ship dashboards without losing our sanity (or our jobs).


I lay out a system that works, from dbt to Metabase, and tell you how we keep analytics tight at scale.


Read it here: Analytics Stack for Speed, Clarity, Control



My most popular LinkedIn post this week

It’s about writing online and the lesson I stole from my 9–5.


image


Why I wrote it: Because it’s not another “I made $5k/month in my sleep” story. It’s about writing when you’re not ready, when you don’t have time, when it feels like no one cares.


Spoiler: those are the moments that matter most.


Read it here: This post on LinkedIn



Here’s how you can help me this week

If any of these hit home:



Seriously, it helps.


I’ll keep showing up, sharing what I learn the hard way.

If you’re on this ride too, I appreciate the hell out of you.


Talk soon,

Yordan

Share
Get the next issue in your inbox
Free, and you can unsubscribe any time.

0 comments

More issues

All 75 →
#10 Jun 7, 2025

Translate jargon with a biz glossary

Read issue →
#9 Jun 6, 2025

Turn demo fatigue into dialogue

Read issue →