This is one of the most comfy chairs I own, reproductions are affordable, and they are gorgeous. The recline is comfortable while still allowing non-desk work (the Eames is *too* reclined for my taste), the arms are wide enough to curl up in, and the back is high enough to support your head. Many reproductions allow adjusting the recline tension.

You'll need to supply your own power and a stand for the laptop.

1. Integrate the documentation with the application. Treat it like code rather than as a separate document.

2. When new features are proposed, plan them by FIRST forking and changing the documentation, THEN implement the change based on the change in the story. This not only guarantees good documentation, it ensures the developers are all on the same page about what the changes should/shouldn't do.

3. Focus documentation on the common tasks, software limitations, and side-effects. Far too much documentation wastes reams of paper telling people "to create a new widget, click the New button." If the "New button" is hard to find, difficult to click, or does something other than creating a new widget, that is a failure of the UI, not the documentation.

To put this in perspective, 5,000 sq. mi. is a square about 71 miles on a side. Compare this to the total area of the Gulf (615,000 sq. mi) and you'll see this "dead zone" occupies just 0.8% of the Gulf. Is this something that needs addressing? Absolutely. But it's not some horrific cauldron of death like the headline tries to make it out to be.

In my experience, the word "Enterprise" usually means a shitty piece of uselessly generic and hopelessly complex software combined with an expensive consultant team who spend 5% of their time configuring/using the software as intended and 95% of their time hacking around its limitations by glomming on little "tumor" systems to shoehorn it into your business.

But I admit I'm a little jaded.

Not to be a grammar nazi, but why did you single-quote the word 'emulating'? Did you mean it ironically or something? The word itself seems to be used correctly...

And no matter how much evidence the US or Ukrainian government produces, no matter how detailed and annotated, Russia will dismiss it with a wave of a hand as fabricated, slanted, biased...whatever they want. They'll never admit responsibility.

Yes, because UN peacekeepers have such a long, sterling reputation on stopping stuff like this from happening.

But regardless, the UN will never do anything in this conflict. Russia holds a veto in the Security Council, and they will stop any such measures from ever happening.

It would also make automated trucking a lot more competitive against human driven transport services...thus the unions will immediately be against it.

Wait...Blackberry? These guys are still in business?

Stroustrup isn't really a great programmer, he's a guy who did a great job marketing a really terrible programming language.

He did. look at the end of the line.

True, but not for under 10 watts...
it's all about trade-offs.

And these are the people we want to trust making decisions about our healthcare?

I love C#. I program in it every day. It's plenty fast, and it's a great language.

However, there are two reasons I would suggest looking to another language.

First, the hottest market for gaming right now is mobile. While it's possible to compile C# for iPhone or Android using Xamarin (along with Windows and OS X), it's not exactly a native experience.

Second, C# (like O-C, C++, etc.) is a general programming language -- it's not in any way specific to the domain of game programming. So, while it's *possible* to design complex games in any modern language, you're probably going to spend *way* too much time dealing with silly stuff like tracking graphics resources and animation loops and simulated physics. You'll have a higher chance of success if you use a language and platform that is more game-specific out of the box.

I would suggest looking into Swift -- it'll give you access to the lucrative iOS market, it's C-like, and it has features that are game-specific. Sure, it's a new language it doesn't compile to Android, but by all accounts it looks like a great language with first-class support for gaming, so you can focus less on infrastructure code and more on the game.

Another option would be HTML5. Depending what sort of game you're looking to build, Javascript and HTML5 may be just the ticket, and there are a number of libraries that can abstract away browser differences and assist with the plumbing needed to make a game run.