Who is Data Gibberish For
You keep the data flowing across pipelines, models, and dashboards. The plumbing is invisible, but every team depends on it.
When something breaks, you’re the first ping. When everything works, nobody notices.
You spend your weeks keeping data fresh, reliable, and affordable. When it’s time to show results, the credit usually goes to dashboards and reports instead of the people who keep them alive.
When budgets, roadmaps, or reviews happen, your work isn’t part of the conversation.
You are looking for playbooks and scripts that make your results visible and impossible to ignore, without needing a different personality or a new job title.
The Cost of Staying Invisible
Being remembered when it matters is the real stake here, more than being recognized in the moment.
When a reorg hits, the work tied to outcomes stays. When budgets shrink, only what’s easy to defend survives.
And when review season comes, “excellent” often turns into “but we couldn’t make a case for more right now.”
Every cycle you wait, the gap grows:
Pay that doesn’t match the scope you carry
Projects that stall before they earn visibility
Work with no proof when leadership asks for outcomes
It won’t close on its own, and doing more work won’t fix it either. You need a way to show what your work is worth before anyone asks.
What’s You Get With The Paid Membership
I build this publication as a system you run.
Every part of it turns technical outcomes into business wins, faster and with no second-guessing.
Here’s what you get:
Playbooks ready to use immediately
Live Show & Tell sessions
Playbooks
I share a playbook that takes less than two hours and delivers a visible win this week.
Reprioritize your workload so your time drives impact, not noise
Translate technical results into outcomes that earn budget or headcount
Push back on unclear requests without sounding difficult
You also unlock the full archive of playbooks to act on what matters now.
Live show & tell sessions
Once a month, I announce a topic upfront. Anyone can join live, but only paid members can turn it into a coaching session and get their own problem fixed on the spot. If nobody does, you still walk away with the playbook.
The recording afterward is for paid subscribers only.
How it works
You get posts, workshops, and templates directly by email or in your feed.
You don’t need extra hours or perfect timing. I build this for engineers with full plates and real deadlines.
1. Pick one playbook
Start with what fits your current challenge: budget, visibility, or scope. Each takes under two hours and helps you land a visible win within a week.
2. Use the scripts
You get the actual words for Slack, meetings, or emails, the same ones I use as a technical person talking to non-technical stakeholders.
3. Join the Show & Tell
I announce the topic upfront. Paid members can turn it into a live coaching session for their own problem, or you get the playbook either way. Anyone can join live, but the recording is for paid subscribers only.
What happens next:
Day 1: pick your playbook and start the steps
Day 2-3: apply it inside your current sprint
Day 4-5: use the script to earn a “yes” on something that was stuck
You’re doing this alongside other people already running it in messy, real-world orgs.
Frequently Asked Questions
“What if I’m not a manager?”
That’s exactly who I build this publication for. Most members are mid-level or senior data engineers who want more ownership, budget, and clarity, without waiting for a title change.
“What if my org is chaotic?”
That’s great. These playbooks work in the real world, with changing priorities, unclear specs, and competing goals included.
“I don’t have much time.”
Each playbook takes under two hours and fits inside your existing workload. You’ll see results without adding more work.
“What if it’s not a fit?”
You have 7 days to explore everything and get a refund if it’s not what you need. No questions, no forms.
Why I Build This
I was a great engineer. I moved to senior fast.
Then I got handed a team, and I was terrible at it. I kept acting like an engineer instead of a lead. Someone left because of me. I hated the politics that came with the job.
So I left. I joined a new company as an individual contributor, and I turned down every lead offer that came my way for years.
I read the books. I listened to the podcasts. Mostly I learned by watching the good leaders around me and paying attention to what they did differently.
Then one day, someone told me I was already leading a team. Nobody forced it this time.
I love it now.
I spent half my career pouring everything into the technical side of the job and ignoring the other half. That other half decides your scope and your pay. I learned that by failing at it first.
This is what I wish someone had handed me back when I got that team and had no idea what to do with it.
Who I am
Today I’m the Head of Data Engineering at a global fintech company, and I was named one of my country’s Top 100 Tech Talents, the only data person on that list.
After years in the big city, my wife and I decided that was enough. We built our own house, and we’ve been living here for the last ten years. Best decision of my life.
Outside work, I do a bit of everything: DIY (I’m decent with electricity and building), computer games, reading, and lately, learning Mandarin. My superpower is that I only need four to six hours of sleep a night.
That’s what I teach here: the part of the job that has nothing to do with your code, and everything to do with whether your work gets seen.
You have two paths from here
You can keep reading free posts and using the free course and eBook. They’ll build your awareness and momentum.
Or you can upgrade and get a repeatable way to turn that momentum into results you can show, and credit for them.
If you’re ready to turn your technical skills into lasting impact, this is where it starts.
