Personal Insight On "Your Identity Is Not Your Code"

One of my developers shared this article via Twitter. That was about a week ago. Just finally getting caught up today on my readings. I'm glad I didn't pass this one along.

My initially impressions after the first three paragraphs: This is spot on! How coincidental that this is also playing along in the background, perfectly accommodating the epiphany?!

Immaculate Crucifixion by Juno Reactor

"I know when I first began, I cared a lot more about how people would perceive the code I wrote rather than how well it solved the problem at hand." Couldn't have said it any better. Now as I'm trying to embrace more of the senior and management role, I realize I need to give on this a bit and focus more on the greater good of the team.

"Criticize the code, not the developer." This is important to remember time and again. I've once said something nasty about some code, primarily due to the frustrations of having to fix something as we were trying to release to production. It really should've been something nasty about the code, not the developer. Little did I realize my harshness was more than heard, as the developer who wrote the code was sitting next to me; he could also see and feel my reactions. This went above and beyond the regular levels of what would be defined as objective criticism. I felt horrible after making this realization and have been much more careful about my criticisms since, particularly focusing more on when and how to deliver them. Essentially, tact.

"Cut the ego. Stop equating bad code with bad developers. Stop equating code criticisms as a knock against you as a person. We could use more people submitting ideas and less animosity around existing code." Enough said.

Working on it one day at a time.

Ref: http://collectiveidea.com/blog/archives/2012/03/16/your-identity-your-code/