I've got to second this. I've seen so many people where I currently work get laid-off but we all know they were really fired. (The company didn't feel like building up the case for termination with cause. Since they're an at-will employee that's ok, the company just had to pay for unemployment.)

In that you can not consistently get more than 40 hours of work out of anybody except a very, very, small percentage of workers. As in I've worked in IT for almost 20 years and never actually met anyone that I saw produce anything like 40 quality hours worth of work a week. (A lot of them thought they were. Then again they also thought they worked far faster than they really did. Giving estimates that were actually half the real value.)

Being able to write readable code. It's a very rare skill.

I can think of one thing in CS that I see gives people with little to no CS education a lot of trouble. Algorithmic analysis, to be specific big O notation. I've seen people not get algorithmic growth at all and end up implementing something that is O(n^2) when they could easily come up with something that's O(NLogN) or even O(N). Surprise surprise when they have to process even a middle amount of data they have problems. I have learned something else though. If someone tells you that their app runs in N^2, log(n), or nLog(n) time they probably know what they're talking about. If they say N! or even C^N they really know what they're talking about. If they tell you it's linear that could either mean it really is linear or that they don't know of any other running time.(Literally I saw code that was obviously N^2 but the developer said it was linear because he didn't know of any other type.)

If your developers are any good you basically don't need to do much. Give them a direction and the tech and they'll happily hack away. That's pretty much what my best manager tried to do. He made sure I had a good machine to develop on, would get them upgraded when they got old, and tried to prevent other divisions from using us as tech support. (Which can happen surprisingly easily since the devs tend to be some of the most tech savvy people around.) So he got that if I'm waiting 20 minutes every morning for my machine to start up or have to reboot once a day because my machine slows down because of all the corporate stuff on the computer that not only ticks me off but actually costs the company money. (Since developer time is actually very expensive so don't waste it.) I'm always surprised when managers can't get the budget for a new laptop or even just an SSD when they thing will pay for itself so quickly. (Back the envelope calculations even if you assume 30 minutes wasted a day a SSD pays itself off in a few weeks, the laptop pays itself off in a few months.)

Would have to have all of the following attributes.

It would have to act very quickly since for most people if you do nothing it's over in 7 days.

It would have to be very safe because for most people if you do nothing it's over in 7 days.

It would have to be very cheap because for most people if you do nothing it's over in 7 days.

The sad thing is that when the supreme court ruled this was ok then it didn't matter it was bullshit, it was case law that the dogs worked. At this point I would literally not be surprised if the supreme court actually ruled 2 + 2 was 7 and then as far as the courts were concerned 2 + 2 really is 7.

Or this one from Plato which doesn't end well either. http://en.wikipedia.org/wiki/A...

Of course I could point out that in the 10 years before PA 38 people were killed in mass killings. However in the 10 years after PA 48 people were killed in mass killings.(I use 10 years because that's what he said in the video. Yes, it reduced the number of shootings but dead is still dead.) http://en.wikipedia.org/wiki/A...

Well that's only true if you can see the entire screen at one time. If you were to simulate a 4k monitor but had the software display it closer then you'd have to turn your head to see the entire thing. (Admittedly maybe you'd have to simulate a 90" monitor at a couple of feet.)

Since in work I have a couple of 20" monitors. It looks like I could use this with the rift to simulate 50 or 60 inch 4k monitor. (Which would be kick ass for development.)

Since as a software engineer I completely admit you know way more about databases than I do.(You're worth every dollar you get paid.) The problem is so many managers think "Oh we don't need DBA's, you SE's can do it. It'll be just as good. Oh and we don't need release engineers either since we'll save money by having the SE's do that as well." (Yeah, right.)

One problem with CO is if the concentration isn't high enough you will get symptoms of headache and nausea before the person dies.

The fact that the least successful division at Sega(SoJ) in the end was making all the business decisions. (You know, stuff like when to launch the Saturn in the US. They couldn't have did a worse job on that.)

Since he was generally referred to as that hip, edgy, young comic that appeals to college kids. That's was a problem when he was 40 but now he's in his 50's. (Getting old sucks btw) I'm wondering how his demographics are now. I wouldn't be surprised if to the college crowd he's now "The guy my parents like"