91–100 of 161 posts
but from
https://www.youtube.com/watch?v=H4vMcD7zKM0&feature=youtu.be...
"All of SREs have to pass a full software interview to get hired"
Earlier quoted context omitted.
> Mostly just stuff any competent company would/should be doing. it's google though, so they act like it's super awesome. Yes, you're absolutely correct. But here's the thing - it was actually Google that pioneered many of this. Many of the big/competent companies that are following these practices are because of Google's "DNA" leaking into those companies (via former employees bringing along the best practices learn…
Microsoft used to have the best practices and...they were mostly as good as Google. Everything old is new again.
Is section 3.1 "20%" time still true?
You guys seem to think that Google is benevolent by giving engineers that 20%, while in fact they do that for very selfish reasons: it is all about copyrights. They hire the smartest Software Engineers in the world, so it is only a matter of time that some of them will create new, disruptive product. If they weren't given that 20% of time at Google they would do that anyway, on weekends, but since they do it in compa…
What did he say that makes you think that?
Earlier quoted context omitted.
You guys seem to think that Google is benevolent by giving engineers that 20%, while in fact they do that for very selfish reasons: it is all about copyrights. They hire the smartest Software Engineers in the world, so it is only a matter of time that some of them will create new, disruptive product. If they weren't given that 20% of time at Google they would do that anyway, on weekends, but since they do it in compa…
Companies own your work even if you do it off the clock, in many cases.
Although there is a well-defined process for launch approvals, Google does not have a well-defined process for project approval or cancellation. Despite having been at Google for nearly 10 years, and now having become a manager myself, I still don’t fully understand how such decisions are made. The reason why I quit Google.
Unless one absolutely does not care what one wishes to work on, joining Google is throwing your future into the Hogwarts hat of an ill-defined cabal of billionaires to pick your job at Google. Sometimes that works out, but most of the time you are allocated to whatever mission-critical project is currently leaking buttcheeks.
In my brief time there, I was placed on a 7-person team that lost one person per month. That is the single worst retention rate I have ever seen. I left after 4 months for that and the realization that the powers-that-be were in denial about the coming impact of an emerging technology that they have since embraced a year or so after my departure.
That said, the SCCS and the build process were top-notch.
But there are good reasons why despite all the perks and smart people, Google's overall retention rate is barely a month longer than Amazon's.
http://www.slate.com/blogs/business_insider/2013/07/28/turno...
> Software engineers at Google are strongly encouraged to program in one of four officially-approved programming languages at Google: C++, Java, Python, or Go. I wonder which of these languages they use to develop the google front page or any other frontend when no Javascript is allowed...
Earlier quoted context omitted.
Companies own your work even if you do it off the clock, in many cases.
That's not the case in most states, like California, New York and Massachusetts, due to state laws.
Given that you work on your own time and don't use company's resources.
Interesting, compared to what's common in the automotive industry it doesn't even mention the terms "requirements", "specifications", "estimations", "project plan", "tracability", "UML", etc...
Right, if it mentioned those, search would still be the version we saw in 2007. None of the other products would exist yet because they would still be conducting user studies based on wire frame mock ups of workflows designed by committees of behavioral psychologists. That's a bit dramatic, but when your product development has a fast turnaround for fixes (git push vs 100 million dollar recall) and it won't kill peop…