📌 Want to play with it? Check this link, but keep in mind the lanugage may look like Klingon to you.
frequencies.ivanovyordan.com/?utm_source=...
01.03.2026 16:43
👍 0
🔁 0
💬 0
📌 0
📌 Want to play with it? Check this link, but keep in mind the lanugage may look like Klingon to you.
frequencies.ivanovyordan.com/?utm_source=...
Stop buying software for simple problems.
AI makes the "build versus buy" decision easy by turning logic into tools.
I replaced years of messy spreadsheets with a custom app for Bulgarian ham radio frequencies in one afternoon.
Stop adapting your workflow to a rigid vendor UI.
By the way, I am running a promotion with a massive discount. Don't miss it.
www.datagibberish.com/subscribe?ut...
33. Learning to say "no" is a senior-level requirement.
34. Your career is a product you must manage.
35. "Joins" are not a business term.
36. A meeting about a meeting is a leadership failure.
37. A dashboard is useless without a triggered action.
Which number hits closest to your current reality?
27. Most people lack attention to detail.
29. Burnout happens when you stop seeing the impact of your work.
30. If the CEO's numbers do not match yours, yours are wrong.
31. Incentives drive behavior more than mission statements.
32. A "temp fix" usually lasts five years.
22. Hire for curiosity over syntax.
23. Ask "why" five times before starting any task.
24. There's no AI strategy without data strategy.
25. Validate your inputs at the source.
26. Remote work requires 2x communication.
27. The first 80% of the project take as long as the last 80%.
15. Business problems stay the same for decades.
16. Small teams move faster than large ones.
17. Data quality is a social problem.
18. Empathy makes you a better engineer.
19. The best code is the code you delete.
20. Under-promise to protect your reputation.
21. Do not build what you can buy.
6. Spend your brainpower on the hard stuff.
7. Hire people smarter than you.
8. Your hardest bug is a typo.
9. Share the credit for wins.
10. Hard skills get you the interview.
11. Soft skills get you the promotion.
12. No one reads the README.
13. A "quick question" from a VP takes four hours.
I turn 37 today.
Here are 37 lessons from 16 years in tech:
1. Tools change every three years.
2. Stakeholders do not care about your tech stack.
3. A simple SQL script beats a complex framework.
4. Excel is the most popular BI tool in the world.
5. Most requests need a conversation.
Tenure is not impact.
Sitting in a chair for years does not earn you a promotion.
Senior engineers hit a ceiling because they wait for permission.
Stop fixing pipelines.
Start fixing business risk.
Solve next-level problems today to get the title tomorrow.
www.datagibberish.com/p/how-to-dis...
Want to know how prioritization got me 40% salary increase (without changing my job)?
Check this story: open.substack.com/pub/datagibb...
"I am busy" is a weak defense.
It invites people to negotiate your time until you break.
Use a priority shield.
List your top 3 projects.
When a new request arrives, ask:
"Which of these should we stop to do this?"
Shifts the burden of choice.
You stay sane.
"Nobody will pay you to sit in front of a computer all day."
My dad said this when I told him I wanted to study Informatics.
We were broke. Exam fees felt impossible.
Today, I’m doing the work no one understands. But it matters.
Skill matters. Confidence sells.
Build both.
What is the most useless feature you were forced to build?
Seniority is a trap.
The better you debug, the more bugs you get to fix.
Staff engineers do not win by shipping more code.
They win by saying no to low-value requests.
The shift:
- Junior: I can build that.
- Senior: I will build that.
- Leader: We should not build that.
This post inspired by a very cool Substack article:
open.substack.com/pub/thedatag...
Living in post-Modern Data Stack times is nice.
The hype is over. The hangover is here.
We spent $150k on tools to move CSVs.
Complexity was a status symbol.
Now, we focus on basics:
- Use Postgres until it breaks.
- Write clean SQL.
- Delete the diagram.
Back to engineering.
Never heard o this one. Thanks, Yura!
Data folks write terrible code.
Here's what I mean
I sometimes see folks using:
- linters
- formatters
- tests
But I rarely see them measuring:
- test coverage
- cycomatic complexity
- code maintainability
Either start writing good code.
Or stop complaining about AI slop.
When you act like a service desk, everybody treats you like a service desk. Nobody asks for your opinion.
You might be essential for strategic projects, but nobody mentions your name and you have nothing for your CV.
www.datagibberish.com/p/the-custom...
AI replying to comments written by AI under an AI generated posts.
What a time to be alive!
www.datagibberish.com/p/data-engin...
Talented engineers leave when the process stops them from finishing work.
They move to companies where the system handles the friction.
A senior engineer spending 20% of their time on deployments costs the company one full day of salary every week.
www.datagibberish.com/p/deployment...
I have no skills.
Not a single one.
Should I feel left behind for not using OpenClaw?
Podcasts are FREE
Blogs are FREE
YouTube is FREE
Learning is FREE.
What's stops you then?
The best way to train a senior DE isn’t a code review.
It’s letting them ship a design you know will break.
Technical intuition is forged in the cleanup, not the doc.
Let them fail safely on internal stakes. No blame. Just scar tissue.
Stop protecting them from growth.
Want the framework? Check my latest article.
Passing The Senior Data Engineer Interview: Build This Pipeline
open.substack.com/pub/datagibb...
How you pass a whiteboard interview:
- Define the problem first
- State assumptions early
- Explain thought processes aloud
- Focus on logic over tools
Technical skill is required but problem solving communication is superior.