Studies have been done and have confirmed that quiet cars get in more accidents at lower speeds due to their sound levels.

I'm sure you meant to say their most precious possession.

It can be if the transparency of the glasses can also be locally controlled, a bit like the 3D shutterglass technology but at a much higher resolution than left eye/right eye.

Could have been worse - could have been complete mrs.

As an EE user I have to disagree. It actually stands for "Eencredibly Eencompetent."
As I discovered when they contacted me to suggest I go from Pay-As-You-Go to Pay-Monthly, on a plan that was actually financially advantageous. Only to find out the next time I was abroad, a week later, that there was no roaming activated on Pay-Monthly. I spent a week attempting to get through to customer service with no success ("We estimate we'll be with you in 1m", for an hour and a half). When I finally managed to get through to them back in the UK, they gleefully told me that roaming could only be activated on pay-monthly if you'd been with them for over a year (W... T.... F.....).
I calmly explained that it was *them* that had contacted me to switch plans, when I'd been using the roaming facility on my PAYG for a week out of every month in the past year, so could they kindly get their thumbs out of their arses and fix it or cancel my plan entirely. And suddenly it wasn't so much of a problem to instantly activate my roaming.
Why am I still with them? Best coverage in the UK and abroad, and best prices for my (very non-average, admittedly) usage pattern. But holy shit, are they ever incompetent.

Just hope you won't be there during one of the Mass Extinction Events.

No, no no. Never argue with an idiot. First they drag you down to their level and then they beat you with experience.

I'm really good at this! Most of the time even *I* can't find my keys.

As someone who's been through a PhD program and dropped out in disgust, and has subsequently interviewed quite a few PhDs for industry jobs: baloney, it's pretty much as the GP describes in a great number of places. It's a highly-politicised who-do-you-know academic circlejerk. And PhD work is usually nowhere near as "intense" as proper high-level real-world work anyway (something a lot of them learn to their detriment in the first few months on the job).

Whoa, hold on there, now we're not just talking about PhDs, we're talking about PhDs with actual real world experience. That's a much smaller subset than you imply, and quite a few of that subset had *failed* real world experience that made them go back to PhDs. Someone with a PhD who's made it work in the real world is extremely valuable, because at that point you actually have evidence that you really have found that smart, motivated, ingenuous person with serious specialization who can be forgiven for naively believing the academic fairy-story that a PhD would actually be valuable outside of the world of academia.

Indeed.

"The minimum to keep the thing working" nearly always implies improving the code. All developers need to realize this and stop this silly false dichotomy between "maintenance" and "refactoring".

90% is a small number, right?

I'm joking, I've never had to work in a truly dysfunctional shop, and yet "fear-driven development" tends to make an appearance whenever stress levels get higher. Pressure makes people take funny decisions that they think are "safe", such as not touching a legacy code base for another 5 years because "it works and we don't want to break it", until it finally collapses under its own weight and technological advancement (in the case I'm thinking of it was the lack of multithreading and 64bit support).

Often its the fear of other people's reactions if you stick your neck out and get it wrong that will doom you to inaction. It helps to remind yourself and others constantly that you cannot have improvement without change, and the only way to do nothing wrong is to do nothing. Build up trust at detecting and *recovering* from mistakes is at least as important as having a process that avoids mistakes. Mistakes happen. Learn to deal with them instead of expending inordinate amounts of time trying to avoid them.

10. It is pitch black. You are likely to be eaten by a grue.

The comma operator could be overloaded, the parentheses operator can't be.

You could also rename the intellisense DLL which solved the problem globally. That everyone at my company did this was a testament to how bad a pile of shit Intellisense for C++ was in VS2005 and VS2010. It's a hell of a lot better in 2012 - haven't used 2013 yet.