afmp94
CONFESSIONS

Things I got wrong.

Everyone shows their wins. Here are the losses — the mistakes, the lessons, what I'd do differently now.

“Experience is what you get when you didn't get what you wanted.”

— RANDY PAUSCH

SIX CASE FILES

The receipts.

№01
FILED UNDER · Leadership
2022

Hired too fast, fired too slow

WHAT HAPPENED

Scaling from 15 to 89 people, I prioritized speed over fit. We had open positions and pressure to fill them. I lowered the bar on some hires because we "needed bodies." Then I waited too long to act when someone clearly wasn't working out.

THE COST

Team morale suffered. High performers got frustrated covering for underperformers. By the time I acted, the damage was done — some of my best people had already mentally checked out.

WHAT I LEARNED
  • 01 Better understaffed with A players than fully staffed with B players.
  • 02 When you know, you know. Trust your gut and act quickly.
  • 03 Keeping a bad hire hurts everyone — including the bad hire.
№02
FILED UNDER · Technical
2018 – 2020

Over-engineered when simple would do

WHAT HAPPENED

I built a microservices architecture for a product with 100 users. So focused on "doing it right" and "building for scale" that I created complexity we didn't need — service mesh, event sourcing, CQRS, the whole enterprise playbook for a startup.

THE COST

Development slowed to a crawl. Simple features took weeks. New developers took months to onboard. We spent more time maintaining infrastructure than building product.

WHAT I LEARNED
  • 01 Start with a monolith. Extract services when you feel real pain.
  • 02 Complexity is not a badge of honor. Simplicity is.
  • 03 Build for today's scale, design for tomorrow's.
№03
FILED UNDER · Business
2015 – 2023

Avoided selling like it was beneath me

WHAT HAPPENED

For years I thought being a great engineer was enough. I built products and waited for people to discover them. I saw sales as manipulative, something for "business people." I was too proud to ask for what I wanted.

THE COST

Good products died in obscurity. Colleagues who were worse engineers but better communicators advanced faster. I stayed in my comfort zone while the world moved on.

WHAT I LEARNED
  • 01 Selling is helping people understand how you can solve their problems.
  • 02 If you don't advocate for your work, no one else will.
  • 03 The best product doesn't always win. The best-communicated product does.
№04
FILED UNDER · Personal
2016 – 2019

Burned out thinking I was invincible

WHAT HAPPENED

I wore 80-hour weeks like a badge of honor. Sleep was for the weak. I missed family events and ignored my health, convinced it was temporary. "Just until we ship this feature." The goalposts kept moving.

THE COST

My health suffered. Relationships strained. My decision-making got worse the more tired I got, which created more problems, which required more hours.

WHAT I LEARNED
  • 01 Sustainable pace beats heroic sprints every time.
  • 02 You can't pour from an empty cup.
  • 03 Family first, health first, human first — it's a principle now.
№05
FILED UNDER · Leadership
2020 – 2021

Couldn't let go of the code

WHAT HAPPENED

As CTO, my job was to lead, not code. But I kept diving into PRs, rewriting things "the right way," becoming a bottleneck. I didn't trust my team to make decisions.

THE COST

I became a single point of failure. My team stopped taking initiative because they knew I'd change it anyway. Exhausted from doing two jobs poorly instead of one well.

WHAT I LEARNED
  • 01 Your job as a leader is to make yourself unnecessary.
  • 02 Done by the team is better than perfect by you.
  • 03 Trust is built by giving responsibility, not withholding it.
№06
FILED UNDER · Technical
Ongoing

Chased every new framework

WHAT HAPPENED

Every Hacker News post about new tech sent me down a rabbit hole. New database? Try it. New frontend framework? Rewrite everything. So focused on tools I forgot about outcomes.

THE COST

Projects never finished because I was always starting over with "better" tech. Teams got frustrated learning new stacks every quarter. We accumulated more debt from migrations than from actual development.

WHAT I LEARNED
  • 01 Boring technology is usually the right choice.
  • 02 Rails has been my stack since 2012 for a reason — it works.
  • 03 Evaluate new tech in side projects, not production systems.
PATTERNS I'VE NOTICED

The repeating mistakes.

Pattern № I

Speed over quality

I tend to rush when I should slow down. Hiring, architecture, decisions.

Pattern № II

Control issues

Letting go is hard. Trusting others is harder. But necessary.

Pattern № III

Builder bias

I'd rather build than sell. But building alone doesn't create impact.

The goal isn't perfection — it's to make new mistakes instead of repeating old ones.

STILL LEARNING

If any of these resonate, I'd love to hear your story.

I share these not because I've figured it all out, but because I haven't. The best conversations come from shared vulnerability.