Comments from an employee mentioned in the article: https://www.linkedin.com/posts/dhtheriault_my-hot-take-googl...
Reflecting on 18 years at Google (2023)
101–103 of 103 posts
Comments from an employee mentioned in the article: https://www.linkedin.com/posts/dhtheriault_my-hot-take-googl...
Reflecting on 18 years at Google (2023)
Wondering if anyone can confirm this, but.... I saw somewhere that part of the problem at google is how their mono repo code base is so cumbersome that they are more likely and willing to kill services just because of the maintenance overhead of maintaining the code. Any insight from Xooglers? I feel like I read this somewhere on here or reddit, but can't recall the specifics.
Am Googler. I do a lot of work on google3 code health and maintenance. I do not think that this is the primary cause of product turndowns. Messy product design, left-hand/right-hand problems, internal politics, unfunded regulatory mandates, and other organizational complexity seem like much more direct causes. People like to add promotion-focus to this list but I don't actually buy that since there are tons of Google…
Yeah that sounds familiar and sort of makes sense.
I have worked for a company similar in size to Google for a long time. During covid I experienced the highest high of my 18 years here. Flexibility was suddenly rampant (it was forced, but still) in a company that had been stodgy and inflexible since its founding. They began hiring just like Google and every other company did, so jobs were plentiful. This had a 'rising tide' effect on everyone (I got a promotion with…
Some static size organizations such as militaries or professional partnerships try to escape this trap with an "up or out" policy that systematically terminates the lowest performers at each level every year in order to open up more opportunities for promotion. This works to an extent, but causes other dysfunctions and probably wouldn't work in most tech companies.