And none of those things are built in. If you need to carry around a keyboard/mouse or gamepad you lose the main advantage of a phone- that you already have it in your pocket. If you're carrying around special equipment you may as well just buy a handheld device.

Upper management prefers this. I don't think this is anywhere near universal at the lower levels- they realize that the top 10% of developers save their asses. Then again, this is why I work for small companies and startups and not anything outside the tech industry- management at small places is smarter than that or fails quickly.

Its mostly people and talent, but the question of what you're doing is important too. Agile is great for things that are easily visible to customers- UI development or web pages, for example. It fails where you have other systems depending on you- a back end service can't change that quickly or have stability issues. Of course, you can do different methodologies for different parts of a complex system and use each where they make sense.

The problem is the whole Agile mindset says that you don't need to put in thought up front on requirements- they'll just refactor everything mid-project to accomodate changes. Its a wonderful way to make millions as a consulting company- you're never over time or over budget because it was never agreed what or when you'll deliver an end project in the first place.

The problem is you can't avoid mediocrity- most programmers are mediocre. And in more corporate environments the percentage of mediocre and bad goes up, as the really good programmers tend to gravitate towards pure software shops and startups. The trick is to give them parts that stretch their abilities but don't overwhelm them, which requires good management.

The problem with Android is limited controls. No keyboard/mouse, no dpad, no buttons, not a convenient form factor. It greatly limits the type of games it can play. It can soak up a good amount of the casual market, but there's a market for something more. You can make a phone with those controls built in, but Sony tried that with the Experia Play and didn't do too well.

You're going to be installing software that they don't know that has low level access to the hardware and could potentially harm it. Voiding the warranty makes sense to me- they can't be responsible for harm done by software they can't control. It doesn't apply to apps, because the apps don't allow direct hardware access except through the APIs Google has written and tested.

Except nobody's feet are exactly 1 foot. Nor is anyone's 1000 paces exactly 1 mile. If those were truly universal measurements, you'd have some point. As they're not, you don't. And in the long term we'd save money by being on the same system as literally every other country in the world by removing the possibility of tooling mistakes, idiocies like NASA Orbiter problem, and additional cost to companies trying to sell in the US of having to have both measurements in their workflows and computer systems.

I've got an '01 Ford. MPH only, I'm pretty sure. A few years older than that, but not absurdly old to be on the road.

I thought I had read elsewhere that the chemicals she used were from school. I can't confirm, but given the tiny amounts that isn't suspension or expulsion worthy- its worthy of a slap on the wrist for not getting permission.

I've done a bit of everything (firmware, mobile, back end systems, etc), but admittedly have never set up a distributed message queue. I did work at Amazon for 2 years, they didn't use Rabbit or AMQP for their middleware at that time. No idea if they do now or not. But I have friends who do that stuff and talk shop frequently, and they've never mentioned either. I wonder if its not quite as big as you think it is.

Funny; I'd think the conclusion would be that, since blind people are very good at instantaneously filtering out background noise, this test would show them as the smartest people.

Use high fructose corn syrup in the roach motels instead of glucose. I'm surprised they don't do this already, since they use it in everything else.

I think a detention for a day for stealing the supplies and not seeking supervision would have been appropriate. Criminal charges and expulsion definitely not. I like the other guy's idea of having her calculate the amount of heat generated and pressure built up by the reaction to see how dangerous it could have been if she had scaled up as part of her detention.

Never even heard of either of them. Of course there are a few stories of functional languages being used- they're just a sub single digit percentage of apps.