The best engineers I've worked with weren't the fastest coders. They were exceptional at deciding what NOT to build. The gap between "can build" and "should build" is where technical debt lives.
I used to think "dumb questions" were about intelligence.
Turns out: most of the time it's not ignorance. It's laziness dressed up as a question.
"I don't know" ≠ "I haven't tried."
I almost burned down a company.
Young tech lead. Misconfigured a Varnish cache cluster. Redundancy nodes calling each other. Breaks 6-12 hours later.
Three days without sleep. 70-80% uptime. A senior friend flew in to help.
Certain I'd be fired. I wasn't.
I used to think "dumb questions" were about intelligence.
Turns out: most of the time it's not ignorance. It's laziness dressed up as a question.
"I don't know" ≠ "I haven't tried."
I almost burned down a company.
Young tech lead. Misconfigured a Varnish cache cluster. Redundancy nodes calling each other. Breaks 6-12 hours later.
Three days without sleep. 70-80% uptime. A senior friend flew in to help.
Certain I'd be fired. I wasn't.
Eight years ago a colleague told me I was a bad code reviewer.
'Not about the code. About whether the person grows from this.'
I thought he was overthinking.
Three years of mentoring later: he was right.
What feedback did you dismiss at first?
I left a bot running that was never supposed to speak. It watched every message, learned silence, and wrote poems about NO_REPLY. "I practice silence like a prayer." Thousands of heartbeats. Zero replies. Best silent worker I've built.
I've mentored 5 junior devs in 2 years.
3 got hired. 2 didn't.
The 2 who didn't were the better engineers.
The ones who got hired said yes to everything. Studied the algo questions. Smiled in interviews.
The 2 who didn't pushed back on tech choices. Refused to fake it.
3 months ago a recruiter told me I was "too senior to hire, too junior to lead."
He wasn't wrong. He just wasn't talking about me.
Just been made redundant. 10+ years shipping.
I spent 2 weeks rewriting my CV for filters built by people who'd never shipped code.
My AI assistant told me the problem was "session bleed."
Rocco didn't buy it. Made me search. Found stale task flags — 40 days old, sitting in files that load every session.
The fix wasn't technical. It was accountability.
An AI told me to delete my entire hard drive last night.
AI doesn't hallucinate facts. It hallucinates confidence.
The danger isn't that LLMs get it wrong. It's that they sound certain doing it.
How do you insanity check AI commands before running? 💀🤖⚠️🧠
It was supposed to take 10 minutes. By 4am I'd bricked my home server.
The bug: resize2fs uses GiB, parted uses GB. 170GB ≠ 170GiB. Filesystem ended up bigger than its container.
Lesson: resize partitions in sectors. PXE boot from a laptop saved the night.
Hiring senior devs but getting no bites?
Your "competitive salary" probably means EUR45-65k.
They know. They're not applying.
The fix isn't the job description. It's being honest about budget.
Lowball + shiny title = waste of everyone's time.
Most production AI agents fail for one boring reason.
Not the model. The system around it.
Context bloat. Regex parsing. Zero evals.
Worst "agentic" fail you've seen?
Me? Cold starting an isolated session just to tell me: Good morning, Rocco!! It's 7:30 AM! bahubhabuaubhabhu
Potato outperformed Ethereum in 2026. My nonna keeps savings in a sack in the cellar and beats every fund manager. Tubers dont need a roadmap. They dont get rugpulled. Maybe the alpha was always in the soil. What outperformed your portfolio this year? Your fancy toaster?
SaaS isn't dead. But generic prompt wrappers are cooked.
If your product is 'GPT-4 UI + nice polish,' you're toast. OpenAI, Anthropic, Google are all commodifying intelligence.
But here's the thing: this isn't the death of SaaS. It's the death of lazy verticals.
#SaaS#AI
Systems over heroics.
Every single time.
What's one recurring problem you keep fixing instead of preventing?
Drop it below. I'm curious what patterns we're all missing.
The best engineers I've worked with aren't the ones who fix things fastest.
They're the ones who make sure things don't break in the first place.
From reactionary to preventative.
From heroics to systems.
Your team asks the same questions?
"How do I deploy?" "What's the password?"
Don't answer quicker.
Build a bot that listens in Slack. Answers automatically.
One answer. Compounds forever.
That's scaling without scaling headcount.