When I’m developing new code, my usual habit is to do a lot of small iterations. That gives me a little bit of success fairly often. I’m not as happy if I have to work for a long time until I can see something appearing on the screen.
There are a lot of ways to measure an individual’s work performance. When you think of a manager, perhaps you imagine her stopping by an employee’s office to see if he’s in his chair during work hours, or checking whether he’s spending too much time on Facebook.
You know that sinking feeling in your stomach. That horrible emotion that you know that something has gone wrong, seriously wrong, and you’re going to be facing a mountain of pain. That terror that’s even worse than your significant other sitting you down saying “we need to talk”. It’s this:
About a year ago, I convinced our Charles Brian Quinn to take a chance on me. While I had nearly 10 years of experience in developing, deploying and maintaining web applications, I had no Ruby experience, no Rails experience and not one piece of paper certifying me of having any knowledge about computers in general. Despite all these deficiencies, I had done my homework; I knew beyond a shadow of a doubt that Highgroove was the place where I needed to be working.