Considering how many apps are using Facebook's SDK, shouldn't this be something that FB should be addressing? After all, they are the ones making an SDK available to app developers to help with user-login. Shouldn't the presumption of trust rest on FB?
There is a difference between working conditions, and labour rights. America has first-world working conditions, and third-world (or worse) labour rights.
As a non-American, I have a question about two things that stand out for me (and do correct me if I'm wrong): the first is that Amazon pays no federal taxes. The second is that corporations seem to expect locals to pay for things that they can then make money off — Amazon's installation in this instance but also American football stadiums stand out as an egregious example.
What responsibility (if any) do American companies have towards the communities/societies they exist in (beyond delivering value to shareholders -- wherever they may be)?
Over on Reddit, this was posted as an example of what happens when you don't involve an engineer. The comments thread is worth reading, but the primary point that most people make is that with plug and play hardware, you lose things like high bus speeds.
This should be very interesting: I think kids between the ages of 9 and 15 have started to see FB as the social network of old people (millenials and X-ers) and are spending way more time on Pinterest etc. And Pinterest doesn't give a complete social experience. The new myspace just might become the social network for gen Y (or Z or whatever alphabet we have for them :)
There is broad idealogical/political movement in India along the following lines:
"India" was an extremely advanced civilization that suffered under the Mughals and the British. Before these "foreign invaders" arrived, there existed a body of knowledge that remains unsurpassed.
--
This is a revisionist version of history based on cultural supremacy. It has become a compelling political argument, since it contains truisms that are either difficult to test, or jingoism that's hard to resist.
The controversy stems from the truisms, many of which are repeated in Justice Katju's speech. At it's heart however is this idea of India as an ancient nation.
The modern nation state as we know it today was stitched together from multiple nations by the British. Before them, the Mughals also ruled a vast area, but the ruling classes were completely separate (culturally, linguistically etc.) from the people they ruled. And the Mughals never ruled the south, where the Tamils continue to represent one of the last surviving classic (comparable to the Greek etc.) civilizations in the world.
There are those who choose to pick a particular culture as the dominant culture and present that as "India". However, that isn't necessarily true.
Consider this: There are two types of H1Bs in the US. I'm in India, and I have a bunch of friends who went to grad school in the US and were then hired to work at different companies.
The only visa that they get is the H1-B. So, they can't start-up a business of their own, or go work at a start-up. And I'm not sure they're taking American jobs. They get paid the same as US citizens (trust me, they care :)
Then there are the IT chaps who get sent to the US as part of an outsourcing contract. The guys themselves don't get hired — the company they work for (Infosys, TCS etc.) is contracted to do some work and they send a bunch of guys over.
It's called the software services industry and they have positioned themselves as exporters of software in India. In recent times, this has come under some scrutiny, with some sections arguing that they are exporting people and not software. But the projects that they get can be really shitty — maintaining legacy Cobol code and Oracle 1 databases. I don't know if that's work that most Americans will be willing to take.
PS: I have never traveled to the US on an H1B. And I have never worked for any software services company.
It captures everything that's gone wrong with the Indian software services industry — no emphasis on curiosity, exploration, or problem solving. If you think about it for a moment, that's also exactly what's wrong with CS education in the country.
I've been trying to hire a good engineer for the last four months to expand our dev team. We're not a startup — we're part of one of the largest ad/PR networks in the world. We're great paymasters and offer the opportunity to work on some really cool products. And we're based in New Delhi, India.
I've met at least 10 people in the last eight weeks — all of them engineers, and none of them seem to know what we're talking about the moment we say things like NLP or Node. In fact, they're not even curious. Just scared, and uninterested in being pushed out of their comfort zone. For eg, one guy told me he ONLY does PHP using the Cake framework. I asked if he had played around with any other framework, he said no. The only reason he was stuck with Cake was because the place he worked at said Cake, he learnt Cake and he used Cake ever since. I asked about MVC and I got a blank look.
I just wish I could come across another computer engineer (outside the existing team) who's curious about programming, who still thinks it's magical when the code you write translates in to cool stuff happening on your screen and in boxes all over the world. Who realizes that you're not writing software, you creating an experience for a user and every bit matters.
Either they're terribly hard to find, or I don't know where to look :)
This is a terrible article. It almost looks like Sony's PR people are trying to come up with strange stories to make it look like lots of people are culpable for Sony's inability to store date safely.