Not exactly. Some workplaces mandate that you're not allowed to discuss your salary on penalty of being fired. Typically because some people at the same level are being paid vastly different sums and if they were told what they were being paid, they'd reasonably be upset.

It completely depends upon location and brew. Cuban and Turkish coffee are closer to rocket fuel than traditional medium roast coffee, and have differing amounts of caffeine in them.

...and you can't say "the rest of the world" without giving a country. Almost every country has its own method of preparation. Even differing parts of the US have different preparation methods (New Orleans vs. Miami, for example).

I'd have to agree. The sales people generally have a motto of "Anything is possible. Never say no." and set unreasonable expectations.

Coming from that type of environment, though, I've found that generally anything IS possible, as long as you throw enough resources at it and get creative with how you implement it. The first round may not be pretty, but it'll probably get the job done.

Its the salesperson's job to then go back to the customer and explain why what they want costs an arm and a leg and will take a year and a day, but if implemented correctly and to the satisfaction of the customer, they're usually willing to pay for it.

Just tell him straight out that his code is impossible to read. Follow it by explaining why its hard to understand and ask him to make it human readable and understandable. Give examples, preferably from an authoritative source such as a textbook, of ways that he can change his code.

If he can't (I don't know how to write it any other way!) or won't (I can read it just fine!) then fire him, with justification that his code is impossible to maintain and he's causing the company to lose money in the time it takes to maintain his code.

Either way, your company is going to be in the lurch when the guy leaves and the only documentation left is his shitty legacy code. Better to cut him loose now and replace his bad code with good code.

You may be thinking of Saturday morning cartoons of a few years ago. I got up early this Saturday and decided to go look to see what cartoons were on. Sadly, Doc McStuffins, Rescue Heroes, and Thomas and Friends was the closest thing I could find. Other channels where as a kid I would watch cartoons had paid programming or news.

Sadly, Cartoon Network seems to be one of the only channels that has real cartoons (i.e. ones with a plot that don't bother teaching lessons to preschoolers)

So now we know where Skynet started.

I'm sure they do have the imagery. On someone's hard drive. In a vault.1

Google / Bing have the technology that makes it far easier to implement over the web. Why reinvent the wheel when you can have the professionals do it?

The way Minecraft and the assorted mods are going, in 30 years we'll be building a space ship in Minecraft and then sending it to the fabrication plant to be built.

Well, upper management may have gotten off with a slap on the wrist and a fine, but a couple middle management guys were charged with manslaughter.

Your GPU card does more than just output video. The GPUs on these cards are designed for brute force calculations and chugging through numbers. They're designed for physics engines, running through protein folding calculations, and rendering high quality video in real time.

If you want to equate them to a design in the past, think of them as really really really powerful math co-processors. CPUs are designed for short command queues and calculations that are hard to predict the next step, while GPUs are designed for long command queues and easily predictable calculations.

...and we've been using teraflop scale on desktops since 2008.

Oh, you mean the 8% failure rate? Considering Romney had a 22% failure rate at Bain Capital, I think Obama has done a better job at picking companies to invest in.

As someone who also lives in Florida, I can explain.

1. Very little preparation for the type of weather that a hurricane can cause. In Florida, we have storm drains that take away most of the water that a hurricane causes. Add in building codes that require buildings to be designed for hurricanes (typically category 3) and utilities that are designed specifically for hurricanes, and you'll find that down here, things are pretty robust by design. New Jersey and New York didn't have that type of preparation and you had buildings collapse.

2. Record storm surges. In some places, the storm surge was over 13 feet where the harbor was only designed to handle the (then historic record) 12 feet, causing massive flooding.

3. Fires. Gas lines caught fire, causing over 100 homes to burn to the ground.

4. In New Jersey specifically, they had a berm go under water due to the storm surges, causing even more damage.

Ultimately, take a look at the damage predictions and you'll see why its called a superstorm. Wind was only part of the issue.