A Developer’s Lesson on Feedback

A Developer’s Lesson on Feedback

posted Originally published at shakiran.hashnode.dev 1 min read

I built my first React Native MVP for a startup pitch.

I was proud of it… until the feedback started coming in.

Instead of handling it, I passed it to a junior teammate.

At the time, I told myself:
“I just don’t like being told what to do.”

But the truth?

I was tired.
I felt unappreciated.
And I was too attached to my work.

Later that day, I stepped away, came back, and realized something:

The problem wasn’t the feedback.
It was my *state when I received it.

As developers, we think we’re logical, but feedback hits your ego, your energy, and your identity.

That’s why we react instead of process.

This was a tough lesson for me, especially after realizing it’s a pattern that’s cost me opportunities before.

I wrote a full breakdown on:

  • Why devs resist feedback
  • how ego + burnout affect us
  • and how to actually handle it better

Read it here
https://shakiran.hashnode.dev/the-code-wasn-t-the-problem-my-state-was

1 Comment

1 vote
0

More Posts

I’m a Senior Dev and I’ve Forgotten How to Think Without a Prompt

Karol Modelskiverified - Mar 19

Local-First: The Browser as the Vault

Pocket Portfolio - Apr 20

Your Tech Stack Isn’t Your Ceiling. Your Story Is

Karol Modelskiverified - Apr 9

I Wrote a Script to Fix Audible's Unreadable PDF Filenames

snapsynapseverified - Apr 20

Split-Brain: Analyst-Grade Reasoning Without Raw Transactions on the Server

Pocket Portfolio - Apr 8
chevron_left

Related Jobs

View all jobs →

Commenters (This Week)

6 comments
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!