April at Data Gibberish: Everything We Published This Month
May 01, 2026 4:02 pm
I want to make Data Gibberish more accessible for the community. So, from now on, you can get an annual subscription just for $90/year instead of $120/year. On top of that, only now until the 4th of May, I offer 30% additional discount.
This means that you can achieve the same success other premium community members consistently achieve and all you need is to invest only $63.
Here is everything that went out this month, with the one thing worth remembering from each piece.
The Only Data Certification Worth Having
April 1st. I spent years calling certifications a scam. I still think most of them are. This piece is my formal retraction, and a five-question exam you can take right now. Pass rate: 100%. It is honest about what it is, which puts it ahead of most.
She Runs a $10k/Month Business Using Data and AI (and Her Title Says Marketing)
Yana has a director job at a bank and a Substack generating between $5K and $10K a month on the side. She built it with a spreadsheet, an MCP-connected second brain, and one rule: every ask goes in front of a number that connects to revenue, cost, or risk.
The meeting always changes when you show up with a competitor benchmark the business does not know about.
Your Best Work Is Invisible Because You Describe It Wrong
I spent three years shipping great work and getting zero credit for it. The problem was language. Every time you describe your work in technical terms to a non-technical audience, you are asking them to do the translation. They will not.
My Three-Column framework forces you to push any piece of work from what you changed, to what it enabled, to which business metric it moves. Column three is the only one your CFO will repeat back.
How to Run Better 1:1 Meetings With Your Manager
I walked into a performance review expecting a conversation about growth. My manager saw me going deeper into technical architecture. I had spent a year doing leadership work informally, and he had no idea, because I kept canceling our 1:1s and showing up with nothing to say.
Ten minutes of prep, three questions, and the willingness to say out loud what you want. That is the whole system.
University Doesn't Teach You Data Engineering. Here's What You're Missing
I talked to Mihail, a software engineering lead who lectures at Plovdiv University.
His conclusion: universities are a decade behind the industry, and data engineering barely exists in most curricula.
The curriculum stops at SQL. Everything the job demands is built in communities, side projects, and conferences. The people who figure that out in year two have an unfair advantage over the people waiting for the curriculum to catch up.
The Operating System Every Data Engineering Leader Needs
Nobody teaches you how to manage a data engineering team. Less than half of data and analytics teams effectively deliver business value, and the primary causes are not technical.
Here I lay out the full OS. Most leaders have a broken rhythm layer. Almost nobody has the memory layer. That gap is where teams fail.
How to Transition from Managing Pipelines to Managing People like Prajakta
Prajakta spent a decade climbing every rung of the data engineering ladder. What she found on the other side: the skills that get you promoted are the wrong ones for the job you just got.
Speed, ownership, and technical control are IC superpowers. In management, they become liabilities. Your impact stops having your name on it.
The engineers who stall at senior are almost always technically strong. What they have not built is the capacity to make others better at building.
Field Manual: How to Ask for a Raise as a Data Engineer (And Actually Get It)
Hamza delivered more in a year than most people deliver in two. He got a stupid 3% raise. He had done everything right technically and nothing right strategically.
The engineer who gets the raise is the one whose manager walks into the budget meeting with the strongest case, and you are the one who writes their sales deck.
Hamza ran my 90-day system. He got a 13,000 euro increase.
The Identity Shift Nobody Warns You About When You Become a Team of One
I asked Yuki, Staff Data Engineer and author of the Polars Cookbook, what the biggest adjustment was when he became a team of one.
He skipped tooling. He said it is a mindset shift: you are no longer a data engineer, you are a data person helping the business with data and analytics.
The technical breadth is visible. The identity shift is not. And the selfishness that works at a large company, where you can negotiate your scope, kills you when the business has no interest in which part of the stack you find meaningful.
82 Resources That Will Set You Apart as a Tech Leader
Nobody tells you when your growth stops. At some point the bottleneck is no longer the code.
The engineers and leads who keep growing past that ceiling are consuming differently: newsletters, books, LinkedIn voices, and podcasts that change how they think, not just what they know.
This is the full list across technical depth, leadership, communication, strategy, and career growth. Do not follow everyone. Pick two or three per category, follow them consistently, and let them compound.
Ten articles. One month. The same thread running through all of them: the technical work is the part you already know how to do. The part that determines whether you stay invisible or get paid, promoted, and trusted with bigger problems is everything around it.
If you are not already a paid subscriber, this is the moment. Until May 4th, the annual plan is $63 total. That is the full archive, every field manual, every paid deep-dive, and everything that comes next.
—
Yordan from Data Gibberish