Comment by Frieren
17 hours ago
> I think same is true for all Big Tech companies. Too many employees doing not enough or quality work.
A lot of people has this feeling because the work at a big corporation is different than in starting technologies.
When you start a new technology everything is new, and a lot of stuff is added at the edge.
When you work for stablished company most of the work is refinements, following new rules or regulations, incorporating products from merges, maintaining technology up to date with new releases... nothing feels important and nothing feels challenging. At the same time, your company fails if it is not done. Quality is also incredible important, to break a tiny component may send thousands of companies around the world spinning.
Maybe you should work for a startup instead of a stablished company. You can move fast and break things when you have no customers, or just very few of them.
> When you work for stablished company most of the work is refinements, following new rules or regulations, incorporating products from merges, maintaining technology up to date with new releases... nothing feels important and nothing feels challenging. At the same time, your company fails if it is not done. Quality is also incredible important, to break a tiny component may send thousands of companies around the world spinning.
This is part of it, but it's also true that in a lot of massive enterprises there is an absurd amount of inefficiency that leads to people effectively having nothing to do.
I had one such role at Splunk, pre-acquisition, which had a mere ~2k or so employees at the time. My entire office was effectively doing nothing; we were the result of another acquisition and management had no idea what to do with us. More hours were logged at the foosball and ping-pong tables than in front of an IDE. I'm not even exaggerating. I left after 9 months because I was bored; I did not write a single line of code that got used in any real application, internal or external.
When I went to AWS, it was closer to what you're describing; it took a lot of work to do seemingly very small changes for the reasons you mention. But I would never say that my team there had too many employees doing not enough work; everyone was busy all the time, it just took a lot of work to do very small changes.
No thank you. I worked in multiple startups and they inherited the worst cancers of big tech: moving slowly, decisions by committees, leveling (in one startup, the founder decided to have six engineering levels in a company with less than 10 engineers). Compound with low pay and erratic behavior of founders, I had seen more than enough.
> When you work for stablished company most of the work is refinements
At what point is a company established? I recall that the early years of Google, it produced not only Search but also Gmail, Maps, Translate, Android, and Chrome. That was all between 1998-2008. At what point did most of Google's work become refinements?
My point being, it is a culture issue. Google could have become "established" and focus on "refinements" after Search. Or Gmail. Or Maps. Or Translate. But each of those times, it did not.
In the years since, Google has spun up GCP from nothing, built the foundations of the current AI boom, designed its own chips (TPU), rolled out self-driving cars, etc.
It's possible for both things to be true at once: a huge company can contain pockets of innovation, pockets of people doing nothing, and a lot that's somewhere in between.
Android and Google Maps were both acquisitions, and Chrome was initially based on WebKit. I don't know when exactly Google started focusing on refinements, but I think it was before 2008.
That is not to say that nothing since then has been impressive, but I do think it's fair to call just about all of it incremental.
In August 2006, Google's then CEO Eric Schmidt joined Apple's board.
Andy Rubin, the founder of Android had already made a name for himself in mobile technology. In 1999, he co-founded Danger Inc. Microsoft bought Danger in 2008.
Google acquired Android in 2005, before the iPhone was unveiled in January 2007.
The rumor here is Eric was shown an early iPhone product, and saw how much better it was than the then-current beta builds of Android. https://betawiki.net/wiki/Android_1.0_April_2007_build
Chrome was based on WebKit, which was based on KHTML, the browser engine from KDE. The only reason we have WebKit as an open source engine is because Apple had to open source it. https://blogs.kde.org/2007/10/26/web-diplomacy/
They released "just" enough of it that WebKit could be replaced in Safari. That's it. Their patch would not compile or run on Linux. It would be _years_ before KDE had a WebKit browser. KDE took months to implement many changed from WebKit into KHTML.
Sequoia Capital introduced the Where2 team to Google. https://www.smartcompany.com.au/technology/neural-notes-how-...
Sequoia were freaking out. They had signed a term sheet with the Where2 team, and backed out because Yahoo! just released a map product. Yahoo was involved in both Google's early history and the events that led to Google Maps. Yahoo had an early opportunity to license Google's search technology, rather than acquire Google outright. Larry Page and Sergey Brin were introduced to Sequoia investor Michael Moritz through Yahoo co-founder David Filo.
Yahoo CEO Terry Semel reportedly offered around US$3 billion to buy Google, but Page and Brin declined.
Sequoia withdrew its proposed investment in Where 2 in 2008. Thinking Yahoo would dominate the market, and it was not a safe investment.
Sequoia then introduced Where 2 to Google. CIA, Keyhole, it's all a fun little rabbit hole :)
When you start hiring former management consultants into leadership positions
I work in oil and gas manufacturing and we are slow dinosaurs when it comes to adapting or using new technology.
Recently we've hired a few startups for PoCs regarding to data analytics and they all get deeply frustrated at the pace it takes us to even agree basic details.
What sucks about these situations is that middle managers want arbitrary things. Their imagination is tainted by existing inefficient processes and systems; they cannot see past these flawed abstractions. So when you ask them what they want, they say stuff like "faster horses" and then spend months debating the color and genders of the horses and what shape the carriage should be... The person who wants to sell them a "car" has no hope.
Yeah, at least in the pre-AI times I was writing way less code than in my startup days. but like 10 to 1000x people actually interacted with them.
OP might have been stuck in a dept that is winding down to prep for a layoff or something. I probably would have stuck around unless I found a different role. Who knows, you might just get some severance.
> following new rules or regulations
I'm ISO27001'ing my company and I wonder if some day, we'll find a better way than written policies, procedures, forms, evidence and audits. To me, it seems like our current world's biggest flaw: We're losing 2/3rd of our workforce to maintaining procedures, they make the work boring and unbearable, and they're not even efficient, even if they do provide upside in systematically organizing things. Standards (when pushed to procedures, forms and audite) are the regression-to-the-mean of collective organizations.