It may take a few tries, but a lot of places don't do background checks, and some that do won't care too much.

I know a guy who several felony, recidivism, his mug shut come up as the first hit on google if you google him... and he was able to get a job in a few weeks.

Fair, but then it has nothing to do with the platform. Windows has a lot of flaws, but requiring a lot of IT people to maintain a large number of them is not one of them. Domain policies, centralized app deployment and management out of the box and all the features you'd expect have been in for a very long time and work very well. Its one of its strengths, not weakness.

Except there's support included when you get a Microsoft product. If you're beyond that and don't have a support contract, its $250 to pass the buck over to them if their shit goes kaboom on you.

Once, I was at a company where we ended up with a critical bug in SharePoint ( ::shudder::...that was a long time ago...) auditing.

After going through the support monkey, we eventually had something silly like 12 microsoft engineers and PMs on the line in a conference call debugging the issue with us a few times over a week. In the end they gave us a fixed up DLL, and things were good.

Net bill: ~$250 (give or take).

10 to 1 ratio for mixed environment? Thats insane. There was some incompetence in there somewhere. 100:1 sounds about right, but ratio obviously gets better as you scale up (once you have tens of thousands, you only need a few to handle the centralized stuff, and 1-2 per physical office for hardware related issues).

Game development is the worse plague in the industry. Only finance companies come close, and they're not nearly as bad (because they pay up the wazoo. Game development shops do not).

Too many college kids went in with the thought having their name in the credits of the next Final Fantasy or Call of Duty. Supply and demand.

The main thing is companies have to be up front about what's expected.

We pay you X, you are expected to Y. This includes A, B and C.

Then its simply a business agreement between 2 people, and the software developer has the long end of the stick.

My issue is companies that don't tell you. Sure, you should ask, but really, it should come up in the employment contract or during salary negotiation. I'm perfectly fine with on-call, I'll just ask an extra 20 grands on my paycheck. Usually most companies are ok with that, and everyone's happy. But there has been a few times when I forgot to ask, and not a peep was made about it from their end. Maybe my fault...but then I end up quitting and everyone gets hurt. I have to explain a short sting on my resume, they have to replace me, everyone's losing out.

The focus on getting stability is pretty important. I mean, you can already download the 0.11x builds, and they've been adopted by main branches of node-webkit, atom-shell, etc already.

But some stuff still needs work. ie: until 0.11.14, the SSL pipeline was totally broken (the new async SNICallback was crashing left and right). Just can't release that. At first glance, io.js wants to push faster releases out and get features out faster. These are the same folks who wrote the unstable code in 0.11.x. Its not going to be magically any more stable in io.js.

Honestly, aside from having a build in way to make async stuff sync (for your execSync, and there was a reason I was trying to get SNICallback from >0.11.13.... one of the main use case of SNICallback is for when certs are generated on the fly...and you can't easily do that synchronously...you need the async SNICallback support for that...), there really isn't much thats needed out of node that can't be achieved via NPM packages. Just make it faster, more stable, and we're good.

There's third party support for that via fibers, but thats external packages that have to be compiled, its hell to integrate in the webkit-based shells...so it really needs to be built in, as opposed to having every damn function in the ecosystem have both a sync and an async version.

"These are the emails I need to respond to" (or look at, or deal with, or whatever...not necessarily actually reply to) is what they meant by to-do list. They didn't mean the scenario where people send emails to themselves as todos.

Inbox is basically done that way. You can even flag emails to be "resent" to yourself later. ie: I get my credit card statement along a ton of other emails, so I'll forget to pay it. Instead of creating a reminder, you just flag the email and it goes away. The next day, you "receive" the email again. You pay your credit card bill, then you flag the email as "done".

Thats how it works.

It will depend a lot on where you are. In the "hip" areas and start-up havens, SF, Seattles, Cambridge, NYC, the trendy (or college friendly) languages like Ruby, Python, and even javascript/node, are omnipresent. Stuff like Scala and whatsnot too.

That jacks up demand and salaries. I looked at statistics recently showing Ruby/Rails as the language that pays highest in those specific areas. My personal guess is that a lot of them pay higher to compensate for lack of benefits (vacations and 401k matching as well as bonus structures, mainly), which skews numbers that don't look at the total compensation package.

I'm actually working in one of those companies right now as a javascript dev, and ended up negotiating my salary to totally out of wack level because I was losing a lot in term of RSU, bonuses and 401k benefits compared to my previous role. So on paper, I'm making 30k more than i used to. In practice, I'm actually making less.

I almost never see anyone who DOESN'T use it that way, at least in the business world (of course, ironically, Inbox doesn't support Google for Works yet...)

Emails are basically a queue of action items, a lot of which are resolved as "won't fix", so to speak (ie: spam, marketing emails, etc), leaving in the inbox the stuff you're supposed to get back to at some point.

Inbox is fantastic for that.

Storage vs rendering. JDBC drivers usually use a long for unsigned int, so it wouldn't have been an issue.

Because it just didn't matter. The default was fine for any reasonable purpose. You don't design several years ahead for a 1/ X BILLIONS event that doesn't cause any security issue and doesn't bring your site down. It probably made that particular page mess up for a little while and that was it.

Heck, they honestly could have stopped counting views when it reached the max and just display "Over 9000!" or Psy's logo and saved themselves the trouble.

Now, they fixed the design and it will never be a problem again. If they had used an unsigned int, when the next Psy comes in and bust THAT, people would have been asking "Why didn't they use 64 bit!!!".

So that was it: use the default when it doesn't matter, fix it when it does (YEARS later)

As some already mentioned, that isn't quite true...but even if it was: anyone publishing results showing racial or gender differences at this point will get crucified on the spot.

This is the new "the earth is not flat". Except we're not sure about which way the truth swings yet.

Its an old historical system. Liquor licenses work the same way, and in many areas the cities are starting to rent them out instead of selling them. Better for the city who keeps getting income pretty much as a form of tax, better for restaurants who don't need to fork tens or hundreds of thousands (I don't remember how much a license is worth in a big city) up front that they need to get a bank to finance. And if shit happens, they're not stuck with a worthless liquor license. Sure, its not as good an investment (its just a cost/tax), but restaurants take enough risk as it is when they open.

This should work the same way. Hell, cities could just stop going after Uber and make them pay a "medallion tax" and be done with it. The service may end up costing a little more instead of being shut down in some cities, and we can stop hearing about that crap in the news. Done.

Yup. Its a little like being a landlord (which is probably your example, I didn't see it).

There's statistics depending on the city, where renting out a place is always 10-15% profit over the expenses of owning and maintaining a property. Also, if you go to a bank with a reasonable income and buy a property that already has a tenant, getting financing is reasonably easy.

That basically means that theoretically, over a reasonable period of time, you could buy an infinite amount of small properties, use the money from one to fund the next, quickly make enough to hire a super to maintain the properties for you, and basically have free, infinite income.

But the world doesn't work that way, does it? Anything easy is a race to zero. Yet there's still a 10-15% profit on being a landlord (not even counting the property value going up by the time you sell) Why?

Oh right, the "work" here is the risk taking. You could be getting a tenant that doesn't pay and be stuck trying to evict them (extremely hard in some states) and foreclose on the spot. A street gang could open up shop next door and the police has trouble getting them out and your neighborhood goes to hell. A contractor could get a permit to build a high-rise across the the street. City taxes could go up faster than rent does.

And thus, I know a lot of people who tried to become landlords and ended up in financial trouble. That risk is what you accept to get an easy real estate profit.

This is the same thing. Medallions were easy profit because not everyone thought so, else they'd have been a race to zero too. And thus, the risk manifested itself.