2,808 karma · joined November 13, 2008
I run a game company developing http://fracturedveil.com and help governments, film/tv productions and companies worldwide on issues related to technology, open source and manufacturing.
Seriously, hackers, maybe some on this site, write this software and design this hardware, to do these things. Maybe a better question is why do we as a profession do so?
It might be perceived as riskier, but I would say that it's likely only slightly riskier than funding a startup anywhere else.
I was just in jordan and met a number of Palestinians (expat and visiting from the region) and I can only say that they seemed as technical as any hacker I've met in Cambridge or in the Valley. (this means that I met people as smart and as inexperienced as I've met in those places too)
They work under what we'd consider tougher conditions (less reliable power and rough and tumble internet connections) but that doesn't keep people from experimenting and learning.
As a funny side note, do you know what SICP sells for in Jordan? 11$! (the jd is pegged to the us currency)
It's not always practical to do these docs, but they are out there.
This is one of the great things about open source, through the use of real , trusted open source licenses, we state our corporate intention quite clearly, and then we don't need to have a huge load of paper that accompanies every project.
We don't , for instance, have paperwork clearing the ip on all the projects we use at Google. The linux kernel alone is a huge work of shared copyright. No paper....
All I can act on from this fairness perspective is Google's interactions with Open Source, making it as easy as possible to release code under open source licenses, which I think we're doing a good job of.
Most employers take the position that everything you do in the space is logically competitive. Recognizing that, we, Google, make it very easy to get permission to open source things, but under Google copyright.
We have a process for releasing under your own copyright, but it is not as flexible. That said, we've cleared about 200 (75% of those requested) projects in the last year for copyright release.
It's easy to get knee-jerk about this and get upset, but recognizing the nature of IP in a company and acting on it is infinitely better than pretending the problem doesn't exist and then, in the future, retroactively claiming copyright when convenient. The latter leads to lawsuits and unfair restraints on creativity and competition.
This system works. We've released 10s of millions of lines of code into thousands of open source projects. It protects the employees and it protects Google and the price is a bit of complexity and the odd thread like this.
Also, thanks to this system, Googlers can work on Google equipment and during their 20% on these kinds of projects, which is clearly useful and recognizes that people who work on open source almost universally do so without regard to the machinery or network they use.
You're always better off just buying text ads. (disclaimer: work at google, loves text ads)
142 gigapascals, along say 38,000 kilometers, ain't easy.
(Disclaimer, I work for google, but not on the sekrit space elevator team, which may or may not exist)
This has been the case since october of 2008. There has always been an unlocked option for developers/users. Consumers can buy those too, but they'd obviously rather purchase carrier related phones to save money on the phone purchase.
I don't know of any magic way of testing for that. There are some good signals, of course, such as:
1) pre-interview open source reputation and release. 2) References from people you trust and respect. 3) Publications with significant content written by the candidate.
But I've seen each of these fail, even in combination, in predicting the ability to execute. That said, it's better than nothing.
(disclaimer, I work for Google, and am also waiting for the part about Google in the OP)