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 👇
the-code-wasn-t-the-problem-my-state-was
Top comments (0)