The tone of this is so different from the factual content it was really hard to read. Like a story about a machine that crushed your hand, and you wrote note to yourself that next time it would have crushed it faster had you sharpened the gears first.
What I learned getting acquired by Google
181–190 of 645 posts
Re: What I learned getting acquired by Google
#182Re: What I learned getting acquired by Google
#183The "red badge" thing was very real. It was really weird having TVCs on your team. You'd all work hard together to launch a thing, and then everybody except the red badge would get a celebratory team tchotchke or a team lunch or something. If you asked about it, the manager would say "we can't give Jim things directly because that might be like compensation and they'd be like an employee." There'd be all-hands meetin…
>TVC Apologies, could someone de-acronym this one please.
Re: What I learned getting acquired by Google
#184Earlier quoted context omitted.
Ok but then contractors have the freedom to work whatever hours they want, not show up to the office, and subcontract out their work - right? If so that might be more appealing than being an employee
Not in practice, because they use a hiring entity to dictate the terms. You're expected to show up on a schedule, do the work etc. much like a FTE, but you're not an FTE. I think some folks have this illusion of software contractors that this is somehow common, it really isn't. The norm is you-are-almost-but-not-quite an employee type work environment, and thats at the better places. I've worked at a place where cont…
Re: What I learned getting acquired by Google
#185How would one go about working at google as a junior fullstack developer? I wanted to work remote or onsite in germany but there seem to be no open positions
Brand yourself as a software engineer instead of fullstack developer, network to find a referral, LeetCode hard.
Re: What I learned getting acquired by Google
#186I had to briefly stop reading this. I realize how _someone_'s promotion goal plays a part in a huge team making significant effort on solving a problem or building one of their chat apps.
Re: What I learned getting acquired by Google
#187Is this a happy story? Having read it my takeaways are that they were immediately asked to rewrite their app in Google's way, then a separate research team went off and wrote them a new API for their core functionality. And now given Socratic by Google on the Play Store was last updated on Oct 21, 2020, and is not available for my Android 13 device, so seems to have just died? Kind of seems like Google bought the com…
I'd be pretty happy.
Re: What I learned getting acquired by Google
#188> "At Google's scale, the external world ceases to exist and is only rarely and carefully allowed to enter their walls" OK Google... now I get why you behave that way with your users (no support, product graveyard...) ! ;-)
I used to think about this when I was a kid. If 5 billion people pray to God at the same time and ask for mutually exclusive things, how can he possibly answer or even listen to them all? And it's now up to 8 billion and the problem isn't getting any easier. I guess the answer is God's perfect omniscience is massively concurrent on a scale unfathomable to human computational models and, by existing outside of time, h…
Re: What I learned getting acquired by Google
#189Re: What I learned getting acquired by Google
#190Earlier quoted context omitted.
A few of the offices even have a pool (Google Dublin, and soon Google London) Because the buildings are usually located in very central city locations - I've often used the offices as a way to kill time til' check-in opens for hotels after a long-haul flight (grab food, caffeinate, have a shower, etc) Recently I took a night train between Stockholm and Copenhagen. Showered in the Stockholm office, walked 5 minutes to…
I assume the data centers get to have heated pools