For C++ there is no standard answer, because every C++ shop uses a different subset of the language. There are probably a few things that all of them have in common, but it's unreasonable to expect that any entry level C++ programmer can be productive without support from senior programmers while they learn the local ropes. Even experienced C++ programmers will need a little time to get up to speed on the local style guidelines.

C++ doesn't have an extensive set of standard libraries, either, which means that every shop has its own set. So senior programmers have to expect that new people are going to spend a lot of time getting up to speed on those.

Finally, I think the question is fundamentally bad, because it implies a misguided expectation of immediate productivity. That's a common expectation (hope?) throughout much of the industry, but unless you're hiring contractors for six-month jobs, its stupid. What matters in the longer run isn't what your new hires know coming in the door, it's how well they learn, and think. Because whatever they know coming in is invariably inadequate in both short and long term. One of the things I found very refreshing when I joined Google is that they don't much care what you know in terms of languages, libraries and tool sets. It's assumed that capable people will learn what they need to when they need to learn it, and that any new project involves some ramp-up time before people are productive. On the other hand, given a little time to get up to speed capable people will become very productive. Much more so than the less capable person who happened to know the right set of things when hired.

Even the small payload becomes a big logistical challenge when you're looking at doing it globally, for large numbers of devices and want to make it fast (means having data centers in all regions), and make it reliable (means having redundancy, at multiple levels). Oh, and the "all the data is encrypted" bit may expose regulatory problems, too.

What specifically are you looking for? As an alternative, are there some ways that Android could be improved to alleviate whatever concerns you have? If your concerns are non-technical and primarily about insufficient ecosystem diversity (i.e. insufficient fragmentation), then there's probably not much to do. If your concerns are related to technical problems with Android, or privacy concerns about its relationship with Google, there may well be.

I'm an engineer on Google's Android Security team, and I'm actively looking for things that we can do to address security and privacy concerns. One of the ideas I've been kicking around is a "pre-encryption network tap"... basically, what if you could turn on a mode that logs a copy of everything your device transmits and receives? Most of that data is (and should be!) encrypted, but since most apps and all system services use the framework implementations (yes, plural... sigh) of SSL/TLS it should be possible to hook in and grab the plaintext. My goal here is to enable users to examine what their device is sending, and to whom, because I think right now it's too hard to tell, and because specifically I think there are a lot of erroneous assumptions that Google is receiving a lot of data from Android devices without user permission.

The downside, of course, is that adding such a hook into the system makes it a prime target for various sorts of attacks. So I don't think we would want to do that, not as stated, anyway. Though there may be some variant of the idea that isn't too risky.

Anyway, given a system like that, it should be possible to build an alternative ecosystem of apps and services that run on Android and don't use Google's infrastructure, and that would be much easier than building an entirely new platform. You'd still need to address the problems I mentioned at the top, but at least those could be the bulk of the challenge rather than just another piece of it.

As another alternative, I think if Google became more transparent about how it manages user data and what it does with it, many peoples' concerns would be addressed. But although I make that argument regularly, I don't have the same degree of influence there as I do over platform technology.

Or if you have other concerns, what are they, and do you have any ideas about how the platform could address them?

Yeah, but if you're talking about ground shipping, $4 is about what you pay to ship a cube a foot on a side.

The title is ludicrous. "Court orders UberPop to be banned in all of Italy" really? Who is going to do the banning? It seems to me the court didn't actually order anyone to ban UberPop, so oh well.

Brainstorming sessions don't require large, complex diagrams because large, complex diagrams come out of decision-making processes, and brainstorming is an idea-generating process. Generating ideas in the same meeting in which you make decisions inevitably leads to poor decisions; meetings are for exactly one of exchanging information, generating alternatives, or making decisions.

Plus a lot more to operate the data centers needed to store and sync all that data around. For Mozilla to build that they'd have to find some way to pay for it. Given that people are generally not willing to pay monthly fees for that sort of service, advertising is the obvious option. But to make the advertising effective, it needs to be targeted, so...

How would this be attractive to OEMs? Google already offers an extremely well-developed open ecosystem. Amazon wanted to have their own walled garden, but you're assuming there are OEMs that don't want to do that, but want to have a different ecosystem, and want it enough to be willing to accept smaller sales numbers. What would make them want to do that?

It's HIPAA, not HIPPA.

Normally, the implication of that question is that there are a bunch of blindingly obvious problems which are being blithely overlooked.

So, what are they?

I think unrealistic portrayals of sex create bigger problems than those other examples you cite -- though they are problems. The reason I think that is that the other unrealistic portrayals don't affect core human relationships to the same degree. I hope I'm wrong, actually. We'll know in a generation or so.

One more point: I find your choice of example to be odd, because the US charges against Hamsa have nothing to do with speech; they're about kidnapping and conspiracy to commit murder. The UK's charges against Hamsa are largely speech-related.

Manning or Snowden would have been better examples.

Oh, I'm not claiming there are no problems. Clearly the US does have some big issues at present with some particular forms of restriction of free speech. I'm fairly confident that will get sorted out over the course of the next couple of decades, though. The pendulum is swinging that direction. Not that perfection will ever be achieved, but there really is a strong bias towards protecting freedom of expression.

I'm a Google engineer, and both of these statements are incorrect.

Taking the second one first, Google is not an advertising company. It's a software engineering company whose primary products are most effectively monetized via advertising. Or, sometimes I think it might be more accurate to say that Google is a data center company, since building, operating and utilizing enormous data centers at extreme efficiency is Google's true core competency. If and when Google gets serious about competing with Amazon in that space Amazon will have a tough time keeping up.

Google is moving fairly quickly away from advertising, diversifying into products which are sold directly. Note that nearly all of the speculative new projects that have come out of "Google X" are built around goods and services, more than the sort of low-value (on a per transaction basis) information services that are Google's current big products. No big winners have emerged from that effort, yet, but if one or more of them do "hit", you can expect to see it quickly replace advertising as the primary revenue driver. About 10% of Google's revenues these days come from non-advertising products. 10% seems small, but keep in mind that represents $5B annually, and is up from basically 0% just a few years ago. Non-ad revenues are growing faster than the ad revenues, so the percentage of Google revenue derived from advertising will continue falling even without a massive new business.

Further, culturally, Google never has been an advertising company. It's a thoroughly engineering-focused company, top to bottom.

The shortage of engineers is not imaginary. Google legitimately has a hard time finding enough software engineers of the caliber it seeks. Money isn't the issue; few people who receive an offer from Google reject it. In the context of this article, though, the big problem is that the engineers Google can find are overwhelmingly male, and either white or Asian. Mostly white. Studies done by many organizations, including studies done internally by Google, show that diverse teams are more creative and more productive. In addition, Google's culture is surprisingly idealistic, and people in the company consider it a legitimate problem that the company -- especially eng -- is not representative of the population as a whole.

I think part of that latter point derives from the fact that Google engineers are, if anything, too well-paid. Estimates I've seen put the "1%" line at about $400K annual income, and most senior Googlers -- including engineers, not just execs and managers -- are above that line. Getting paid that much tends to make decent people wonder if they should feel guilty at their luck and their privilege. At the same time, it's not like anyone is going to agitate to get paid less. So a better option is to say "Well, the real problem here isn't that I make too much, it's that not enough people have the opportunity to do the same". In particular, women and minorities.

That last paragraph is purely personal speculation, mind you. Laszlo Bock may not agree at all.

I make better than 300K per year as a software developer, when you include base, bonus and stock grants (which I view as variable cash bonuses, since I have them sold automatically the instant they vest). And I don't have to stick my fingers in peoples' mouths.

Whatever you think of the various sides of this argument, it's interesting to me to look at how different the sides are.

The US is, on average, far more concerned about pornography and other sexual issues than the UK, but there is not and never will be any significant discussion of government-mandated filters, outside of specific situations like government-run schools. The reason is our belief in the importance of free speech. Although there are plenty of Americans who would like to ban porn, no one at a national level says it out loud. No one seriously talks about it even at local, highly homogeneous levels, because everyone knows it won't fly.

The UK is somewhat less prudish than the US, but is perfectly willing to carve out large exceptions to free speech wherever it's convenient. Therefore, British pols do talk seriously about trying to ban porn, except for adults who opt out.

Europe (as a whole; there are exceptions) is even less concerned about free speech than the UK, but apparently considers porn to be something worth fighting for, to the degree that they're willing to invest at least a little effort in fighting to keep porn available to kids in the UK.

FWIW, I think porn is bad. Conceptually, there's nothing wrong with human sexuality, but porn presents an extremely distorted view of human sexuality. I think regular consumption of hardcore pornography, particularly by adolescents, skews expectations and perceptions in ways that have negative consequences. That said, I have no interest in trying to ban it. I do filter it on my home network, but that's a half measure which mostly serves as an early warning system (I get notified of attempts to get to porn sites) which offers a chance to talk the issues over if I find my kids looking for it.

All of which mostly says that I'm a fairly typical American parent: concerned about porn but unwilling to take the strong anti-freedom steps needed to effectively ban it :-)