Software Development Practices At Google
prostoalex writes "It's widely known that Google allows its engineers to spend 20% of paid work time on personal projects (that are nevertheless considered property of the company). But how does the practice actually work? Joe Beda provides a helpful insight in his blog, pointing out other interesting software development practices at Google. The code database is open for everyone, the snippets and pieces are documented and one is encouraged to re-use existing code. The intranet is transparent to the max and the company accepts the fact that there's more than way to accomplish something, so a better method is always welcomed. Interesting to note that just like Hawaiian shirt days in Office Space, the 20% per projects are "actively encouraged" - Joe suspects his review ratings might slip if he doesn't have one soon."
Hang on... we all know majority spend 20% of their time on porn, but labelling it "personal projects".... yeah, could work as an excuse for filling in the efficiency void :)
Three rings for the Elven-kings in the sky
Gnarly dude!
;)
What is this... a 1980s BMX article?
DBA? Software Engineer? My company is hiring! Click
What if you only did 19%?
Or 18%? 17%? Where do they start saying..
"hey...you need to work less on what you are supposed to and more on your side project."
"Hey google what the hell is this yellow stuff in the picture eating my plants"
Spongebob?
How many pieces of flair do they have to wear?
CC Licensed Serialized Story and Podcast: Ingenioustries
"You're fired for blogging!"
If slashdot were owned by a Google employee then that would explain why 20% of the stories that run on /. are about Google.
/bye karma
Let's consider this...
Yeah, I can see how working for such a place could suck...A feeling of having made the same mistake before: Deja Foobar
Does that mean it's personal as in "beer" not "speech"?