[olefoo]

For 1. I'm being generous and reading it as shorthand for; "If your bakery doesn't manage it's presence on the network and patrol it's reviews and it's image online; it's business will be eaten by those of your competitors who 'get it'." I'm not sure why an iPhone is required equipment, but the point he's reaching for isn't entirely lost.

For 2. I'd say he's right in that python has played a fairly large role in Google's developer outreach and seems to be the lingua franca for expressing ideas in code within Google.

The first point is just sloppy, and suggests that Forbes doesn't engage in the outdated and unfashionable practice of editing it's writers. The second is a fairly pedestrian observation about the software industry, that languages and technologies are identified with some entities more than others. That the languages a person who is a developer knows may affect his view of companies that use them is not in question, whether it's a benefit to the companies in question is unknowable.

[taylorbuley]

Forbes contributors (staff and outsiders) are generally copyedited for style but my understanding is that content is generally the responsibility of the author.

This model may not be for everyone but it allows us to bring in great non-staff writers like Timothy Lee (http://blogs.forbes.com/timothylee/).

While contributors can still pitch mag stories there's still a lot of editorial involvement in the print publication.

[hn_reader]

I think the intent of #1 is clear (I agree with your reading of it) but the sloppiness of the statement is distracting. Same really for #2, though it looks like I'm wrong and Google does have three official languages..still I have a hard time believe a 30,000 employee company would not use many more languages internally in some capacity.

[ryanmolden]

>still I have a hard time believe a 30,000 employee company would not use many more languages internally in some capacity.

There are likely uses of other languages internally for small projects or one-off kind of things, but large companies generally prefer some standard practices/patterns/languages. For well written code, you have to realize, your code will likely outlast your employment. That means someone must maintain it, fix bugs, augment its functionality, etc... It is MUCH easier to manage that whole flow with strict(ish) stylistic standards (Google has these) and a small range of possible languages. If you've ever seen code written 15 years ago in the (then) language du jour, with no sort of consistent/recognizable style/coding patterns, etc.. you will understand why companies do this kind of thing.