Bruno Afonso

<start of post>

The most expensive mistake I made as a junior dev had nothing to do with code.

It was my ego.

I thought asking for help was a sign of weakness.

I thought I had to have all the answers.

So I sat in silence for three days.

I was assigned a task to update a legacy database schema.

I didn't understand the migration tool.

Instead of asking, I spent 72 hours "researching."

By Wednesday, I was nowhere.

My manager asked for an update.

I had to admit I hadn't even started the migration.

He didn't get angry. He just sat down.

Why didn't you ping me on Monday?

I told him I didn't want to look incompetent.

Being incompetent is wasting three days. Asking a question takes three minutes.

That changed everything for me.

Now, I follow the "30-Minute Rule."

And it has saved me hundreds of hours of frustration.

Step 1: Try to solve it yourself for 30 minutes

↳ Use Google, documentation, and your own brain. Deep dive into the problem.

Step 2: Document what you tried

↳ Write down the 3 things you attempted. This proves you aren't being lazy.

Step 3: Ask for help immediately after the timer hits 30

↳ Reach out to a peer or senior. "I'm stuck on X. I've tried Y and Z. Any ideas?"

→ It protects your productivity

→ It respects your teammates' time

→ It builds a culture of knowledge sharing

→ It stops "rabbit holes" before they start

I still use this rule today as a senior.

Asking for help isn't a weakness.

It's a superpower for moving fast.

Do you use a time-limit for being stuck? Or do you prefer to grind it out?

#CareerAdvice #SoftwareEngineering #JuniorDev #Programming #GrowthMindset

<end of post>