First of all, you've negotiated a position, understanding the conditions of work. I know that the balance of quality and speed of development I provide speak for themselves. If my employers failed to appreciate the measure of my performance, then I would move on to on that did.. and my former employers would be left to ponder the wisdom of their decisions. I work 8 hours a day, because I really work 8 hours a day with my code hat on, and I will be the first to stay extra hours if I considered myself deficient in my role.

...until morale improves

..that mankind will be robbed of the ritual of the mid-life crisis?

This seems somehow appropriate, it fits in some kind of context: "The Ravenous Bugblatter Beast of Traal is a wild animal from the planet of Traal. It is known for its never-ending hunger and its mind boggling stupidity, indeed being listed in the Guide as the stupidest creature in the entire universe. It is such a profoundly unintelligent animal that it assumes that if you can't see it, it can't see you. - Douglas Adams"

.., a good coder often has such unexpected characteristics. Ir requires a tenacious, unyielding character. The best possible solution is the solution. It's not the smart guy that talks a lot and gets stuck in analysis paralysis. No fear of new approaches, new technologies, huge, bad legacy code that needs analysis. The minimal interpersonal skills to ask questions when they can result in faster understanding. There's no complaining about languages, operating systems, or environments. There's just a focus on the best solution. There's no complaining, that's just weakness and fear. Fear of new is unacceptable weakness. Personality, real personality. You're not a fucking salesman, show some love for people that make you look good, and expect the same. You're never there to stop progressing, if that's your game then go into management. I actually spend a good portion of my time staying off the radar of "tenured" developers, so that I don't piss them off with "new ideas" and "refactored designs. The corporate development world is a simple place, monkeys vying for pecking order while exerting the least effort. Ensure acknowledgement of your work, through whatever means necessary, and subtley set a ground rule that nobody will take credit for your work.

a few pointers.. har har

... of the dark meat

fail boat is fail

..and the biggest problem in enterprise style development is the rut, and the fear of new technologies and ideas. So asking about why manholes are round, or how to build a pyramid, or other such nonsense, it's fun for the interviewer but it's not going to get you the guy that has a sound fundamental knowledge and a drive to keep up with the latest technologies and best practices, and most importantly an ego-free sense of pride in their work.

... but you had me at Plumpergeddon

..and keep paying nerds, lear jets ain't cheap!

the guy that invested time, effort, and money in a degree will get the job. That's 100% makes it worthwhile. Employers would like you to think that you're easily replaced, the reality is quite different.

if the driver falls asleep, you fukkn zap his ass to wake him up? and then write up an electronic ticket and suspend license.. simple solutions people.

cash on the barrel, and don't put all your eggs in one basket.

Almost every position around here is work to hire, and that's based on reality: companies don't want to invest in sales-people for IT positions.