Ever felt like you were an impostor? Like you were just pretending to know what you know, that you obviously were not as smart as you think [http://www.exceptionnotfound.net/you-are-not-as-smart-as-you-think-you-are/], and eventually everyone would find out and expose you like the fake faking faker you are? Good. I've
> You're not paid to write code, you're paid to think. This is one of the first things new hires on my team hear from me. It's a nice concise way of saying I don't care how quickly you finish the task, if its poor code it's as useful as a
I am an enormously self-critical person. If I'm going out to a party, or having dinner, or even just giving a presentation, I'm constantly playing back my speech and my actions in my head to see where I went wrong. It sounds like two awful television sports announcers who follow
Scott Hanselman has an post up called Bad UX and User Self-Blame - "I'm sorry, I'm not a computer person. [http://www.hanselman.com/blog/BadUXAndUserSelfBlameImSorryImNotAComputerPerson.aspx] " It's an excellent read, and in it he discusses the phenomenon of users blaming themselves when something goes wrong when using a computer.
In my opinion there are five basic personas [http://en.wikipedia.org/wiki/Persona] that an effective programmer can utilize to do his/her job efficiently, and they can be combined in ways that might make them more inclined to certain "roles" in their development team. Which one (or ones)