Yordan Ivanov

Head of Data Eng | Building modern systems + sharper leaders
✍️ | 📕

[Yordan Ivanov @heyivanovyordan]

Hari works 7:30 to 6:30 and patches failing systems most mornings.

He still started within the hour.

Busy is the reason to act now, not the reason to wait.

PS: What is the one-hour action you have been avoiding this week?

[Yordan Ivanov @heyivanovyordan]

Action within the hour separates engineers who move from engineers who read about moving.

I coached a senior last week yesterday who wanted ML skills before AI makes his job obsolete.

We spent fifty minutes mapping his path from dashboards to prediction models.

[Yordan Ivanov @heyivanovyordan]

I have watched engineers spend years learning and planning with zero results because they overthink instead of acting.

The perfect plan you never start is worth less than the ugly action you ship today.

Your excuse is probably that this week is too busy.

[Yordan Ivanov @heyivanovyordan]

PS: What goal have you been planning for more than three months without starting?

[Yordan Ivanov @heyivanovyordan]

Big goals fail because nobody knows what to do today.

I walked a senior engineer through the 5-4-3-2-1 cascade yesterday.

He went from AI anxiety to shipping his first prediction model in four months.

Here is the framework:

[Yordan Ivanov @heyivanovyordan]

The method works backward from a vivid future to motion today.

Most engineers plan for months and ship nothing because the gap between vision and action stays enormous.

The cascade closes that gap in five steps.

[Yordan Ivanov @heyivanovyordan]

Rushing into a migration to show value quickly is a big mistake.
Yet, that's what most leaders in data do when joining a new org.

There's always a reason behind the legacy.
Learn the reason.

Then, if needed, do your migration.
There are better ways to impress management.

[Yordan Ivanov @heyivanovyordan]

If you haven't failed, you haven't tried hard enough.

[Gregor Ojstersek @gregorojstersek]

In my upcoming book The Multiplier Mindset, which I’m writing with O'Reilly, I’ll feature 8 case studies of exceptional engineering multipliers.

There are dedicated chapters planned, which will feature case studies of successful engineering multipliers:

[Yordan Ivanov @heyivanovyordan]

@rpmogan 100%! That's very well said.

[Yordan Ivanov @heyivanovyordan]

Scope creep doesn't come from stakeholders asking for too much.
It comes from you never writing down what the project doesn't include.

[Yordan Ivanov @heyivanovyordan]

Keeping a technical opinion to yourself isn't humility.

It's a habit that looks like disengagement from the outside.

When something is heading the wrong direction, say so.
Once, clearly, with a reason.

That's the whole move.

[Yordan Ivanov @heyivanovyordan]

A non-technical manager isn't your problem.

One who stopped trusting your estimates is.

[Yordan Ivanov @heyivanovyordan]

The highest-value thing you do as a senior stops being technical output.
It becomes the quality of decisions made around you.
Most engineers resist this.
And wonder why they keep getting passed over.

[Yordan Ivanov @heyivanovyordan]

Most 1:1s are status updates in disguise.
Come in with one real problem.
One thing you need help with or a decision you need made.
That's what the time is for.

[Yordan Ivanov @heyivanovyordan]

Explaining a pipeline in plain language is harder than building it.
Your team won't like hearing that.

But the VP who funded someone else's project because he didn't understand yours? He agrees.

[Yordan Ivanov @heyivanovyordan]

Your work doesn't speak for itself.
It never did.
You were just hoping it would so you didn't have to.