> Take Jeanine Banks, for example, who manages the department that somewhat arbitrarily contains (among other things) Flutter, Dart, Go, and Firebase. Her department nominally has a strategy, but I couldn't leak it if I wanted to; I literally could never figure out what any part of it meant, even after years of hearing her describe it. Her understanding of what her teams are doing is minimal at best; she frequently m…
Reflecting on 18 Years at Google
241–250 of 1001 posts
Re: Reflecting on 18 Years at Google
#242Seems like they fired the Google Adsense support team. I have been using Google Adsense for many years, and since last year there is no way of contacting any support, there IS NO WAY, I have lost over 10k in revenue because of it, and was only able to get my problem fixed after 2 months by joining a third party publisher network.
Keep in mind that Adsense is one of Google's main sources income, and that they take a 32% cut as an intermediary (So they have ample money to pay for a 5 star support)!
Re: Reflecting on 18 Years at Google
#243Ian's post is pretty incisive, although I've read so many of these over the past 15 years or so. And the prescription is always to go back in time. I don't really think that's possible. When you're a newcomer, a disruptor, the whole point is to be different. You're bold, you have a clarity of purpose, you say things like "we're building a new kind of a company" or "the user comes first." But once you achieve market d…
Google continues to print much more money than it burns. People get hurt by callous corporate decisions like layoffs. People don't get hurt by a company that has insane amounts of money taking risky projects, and if they fail, assigning those people to some other project. Given the size of Google and the fact that they hire generalists, being at risk of losing your project is very different than not being sure about the future of your job.
Re: Reflecting on 18 Years at Google
#244Very interesting they were working on Flutter
I have just spent 18 months with Dart, supporting Flutter development
I formed the view that Fludder (as I called it) was built by brilliant engineers who were directionless. As a replacement for Javascript it is an utter failure, sadly
Made this a very interesting read
Re: Reflecting on 18 Years at Google
#245Re: Reflecting on 18 Years at Google
#246Earlier quoted context omitted.
You are probably right; I just don't really see what's to be gained by going public with it considering the complaints are pretty inside-baseball and not that interesting to outsiders (I mean, hard to imagine someone thinking "I'm not going to deal with Google because so-and-so's subordinates say they don't understand her strategy").
I will certainly not use Dart if a person in charge of its direction doesn't know what they're doing even at a basic level. I can't just blindly hope her team does what's best and doesn't listen to her.
Re: Reflecting on 18 Years at Google
#247Every bit of innovation in the AI space today originated at Google. The company poured probably tens of billions into its Brain division, sponsored and made public every bit of research, and pretty much created the field of modern AI. So what was the outcome? When the employees realized they had struck gold they figured they'd rather go join startups or found their own companies instead, because regardless of the amo…
Re: Reflecting on 18 Years at Google
#248> Take Jeanine Banks, for example, who manages the department that somewhat arbitrarily contains (among other things) Flutter, Dart, Go, and Firebase. Her department nominally has a strategy, but I couldn't leak it if I wanted to; I literally could never figure out what any part of it meant, even after years of hearing her describe it. Her understanding of what her teams are doing is minimal at best; she frequently m…
Nothing kills motivation more than bad management, I can totally feel his pain. In saying that, I don't think public, targeted statements like this are ever the right thing to do. She's just a person, doing a job.
Re: Reflecting on 18 Years at Google
#24912 years at Google for me, 2011-2023. Left after they froze internal transfers the same day I was going to transfer, which put me in limbo for 6 months despite management saying they'd find a way to get it done. Absolutely agree with this article. The disaster of Google+ and "Real Names Considered Harmful" was the first major crack in the culture. The layoffs destroyed what was left. The change in frankness and hones…
I left in 2021, only 3 years tenure. The company was extremely chaotic. We had multiple calls to walkout, unionization, Sundar locking down communication in the wake of people fighting on memegen. We had company wide drama all the time. I had a list of every major dramatic happening and it grew to like 5-6 things in a year. I showed my manager and we laughed about how crazy it was. I left and from what I hear it just…
Re: Reflecting on 18 Years at Google
#250Ian's post is pretty incisive, although I've read so many of these over the past 15 years or so. And the prescription is always to go back in time. I don't really think that's possible. When you're a newcomer, a disruptor, the whole point is to be different. You're bold, you have a clarity of purpose, you say things like "we're building a new kind of a company" or "the user comes first." But once you achieve market d…
Still, the market expects it to keep its crazy growth rate and Google actually has done a good job there. Unless Google decide to shrink its business significantly, I'm not sure if going back in time is a viable option. The problem could be remedied by aggressive reduction of business/operational complexity but it won't solve the root issue. I don't know the solution as well.
But I still agree with the point that Google generally lacks of clear organizational goal/visions. This sort of inter-personal alignment is critical for scaling out any organizations, but Google lost it during its aggressive expansion period in Sundar's tenure. Many teams usually fail to find clear causal, logical connections between their daily works and company-wide OKR. Then mid-level managements tend to develop bad organization signal such as entirely metric driven projects since they don't know what to rely on. I guess this is something more actionable, but might not be easy to solve.