I'm sure all of us are hard working, very dedicated employees who sometimes throw ourselves too deeply into our work. We get the in-the-zone and we are off on the trail of the solution to the problem. Stepping away from the screen when your in hot pursuit can be very difficult. But then there are times when it didn't work. No matter how hard you tried the odds were stacked against you. You pleaded to the project manager but conditions were set that weren't in anyone's control and you or your team need some real pixie dust to make it happen. It's a rush; pulling the rabbit out of the hat at the last minute, but this time it doesn't happen. You or your team have lost.
So, after time, we tend to dodge those hits. We say we are “choosing our battles”; in reality we aren't as motivated to take a chance as we once were. Herein lies the tar pit of a career. Taking this route will only make you a mediocre programmer. I say this because I've been around this cycle. I've watched those around me do the same. I've been at the same company now for almost 5 years and am still pretty much the new kid on the block. (There isn't much of a turn around here obviously) But I've been here long enough to regret some decisions I've made; whether I wrote something or should have written it. I've gotten ambitions about projects that were “canned” for one reason or another. And probably one of the most frustrating lessons has been to understand that nearly everyone outside of the development team couldn't care less about “the process”. They just want it to work. There is no “coolness” factor in milking that last tenth of a second out of the method or the fact that no one has broke the build in over a month. It does make it tempting to just sit quietly with your cup of coffee in your hand and be pleased with what you've accomplished. You know it's cool and a nice accomplishment - but don't do it!
It's a balance of discipline to keep the client happy, making them feel like they are part of the process but keep them out of the system. Usually this turns in to a “Wizard of Oz“ affect jargon speaking and high level talk to keep them at bay, but don't go there either. That's a whole other post for another time. Right now my advice is leave conversations with the client to the team manager and project leader.
In summary - Don't get too comfortable in your cube or office doing your little routine. Get out there. If you've just taken a hit or feel beat up I want to encourage you to stand up dust yourself off and jump back in.