We had a one that sorted a list by javascript. When asked, explicitly, what he would do with 1 million records he said 'the same'.

I never respond to recruiters unless I find proof they actually read my resume.

Lately I have been doing the selections. Boy. I wish people would simply pass the Codility test, find the nullpointer in our test and understand sql injections. I never trust a resume again; have to verify it.

The exorbitant money will come down, in time.

Remember we are still in the pre-industrial era, computer wise ('everything is still manual labour'). That's why IT costs so much compared to the bare-bone costs. That's why we have QA issues. ...

And a cupcake if dummy mode is turned on. I heard lately that harddrives cannot stand low-frequency sound waves. He should have bought ssd's.

I've heard that they often take running servers out of racks (split the power wire, attach UPS, ... ).

You activate your hot-standby. Or you disable that part of you cluster.

Any hoster, datacenter or location can be down because of any number of reasons.

We've been doing business with Cuba too...

Who has not.

Not according to intel

There are two issues with all this multi-core speak we've been hearing:

There is hardly any code, other than a few optimized libraries, that use multi core processors. They try to make it sound unimportant but it is the largest hurdle. There is a reason people don't think of a 3930k as being 50% faster than a 3820! Other than some failed libraries like OpenMP; there are no valid programming models to use either multithreading and/or networking transparantly (since it should not functionally make any difference). Ergo: The developers are still making their single-thread code.

The advantage of multi core processors can be that you can lower you clockspeeds and/or memory speeds on secondary tasks. Hardly any research is done on that (I have myself but let's call that an 'academic' proof of concept).

Ask them how they test the application. Because you cannot change it easily if you worry about breaking stuff.

I work at a SaaS business and I have the complete opposite experience. I have a boss/owner who is in it for the long run. I realize that if our service sucks I need to find another job.

So there are still people being tortured by forcing sharepoint on them? And you have proof? It must be the Iranians and North Koreans.

My boss generally does not touch non-OSS. Only 5 mega-euro throughput though.

Cognitive dissonance reduction. Read up.