I’ve spent most of my life thinking I wasn’t good enough to be a Google engineer, but as I got older, I realized that they aren’t smarter, they just had a better resume. I don’t doubt that some of them are way smarter than me, but most of them are just smart, or at least domain smart.
The FAANG companies have an internal kind of elitisim that would make staff less effective.
If you look at any Google Java library, GWT, GSon, Guava, Gradle, Protobuf, etc… there was a commonly used open source library that existed years before that covered 90% of the functionality.
The Google staff just don’t think to look outside Google (after if Google hasn’t solved it no chance outsiders have) and so wrote something entirely from scratch.
Then normally within 6 months the open source library has added the killer new feature. The Google library only persists because people hold FAANG as great “Its by Google so it must be good!” Yet it normally has serious issues/limitations.
The Google libraries that actually suceeded weren’t owned by Google (E.g. Yahoo wrote Hadoop, Kubernetes got spun away from Google control, etc…).
Every big company suffers from “not invented here” syndrome. It’s not always just because of arrogance. For example, as an engineer at Google, it can be less hassle to use a first-party library than a third-party one.
Also your list of examples is pretty bad. Guava is one I remember filling a real need when I worked at a small Java shop, and as I recall there was no widely used alternative to Protobuf when it came out. Gradle isn’t even from Google at all!
I actually researched my list, most the technologies were used internally for years and either publically released after better public alternatives had been adopted or it seems buzz reached me years after Google’s first release. So I am wrong.
Between 2012-2015 I used to consult on Apache Ivy projects (ideally moving them to Maven and purging the insanity people had written). As a result I would get called in when projects had dependency issues.
The biggest culprits were Guava/GSon, projects would often choose to use them (because Google) and then would discover a bug that had been fixed in a later patch release (e.g. they used 2.2.1 and 2.2.2 had the fix). However the reason they used 2.2.1 was because a library they needed did. Bumping up the version usually caused things to break.
The standard solution was to ask’why’ they needed Guava/GSon and everytime you would find they are usually some function found in one of the Apache Commons libraries. So I would pull down the commons library rewrite the bit (often they worked identically)
Fun side note in 2016-2017 I got called to consult on a lot of Gradle projects to fix the same kind of convoluted bespoke things people did with Apache Ivy. Ivy knew the Gradle ‘feautres’ were a massive headache in 2012 and told you to use Maven for those reasons. Ce La vie.
We tried using Protobuf in 2008 and it was worse than the Apache Axis for JSON conversion (which feels too harsh to say), similarly I had been using AMQP or Kafka for years and tried gRPC when it was released (google say 2016 but I am sure we tried in 2014) and it was worse in every metric I still don’t understand why it exists.
I was using Vaadin in 2011 and honestly thought GWT was released in 2012. I had to use it in 2014 and the workflow, compile time and look of GWT is just worse than Vaadin.
I’ve spent most of my life thinking I wasn’t good enough to be a Google engineer, but as I got older, I realized that they aren’t smarter, they just had a better resume. I don’t doubt that some of them are way smarter than me, but most of them are just smart, or at least domain smart.
I kinda worded it badly, but my main gripe is how difficult it’s getting to get jobs, so this is the only part that matters.
The FAANG companies have an internal kind of elitisim that would make staff less effective.
If you look at any Google Java library, GWT, GSon, Guava, Gradle, Protobuf, etc… there was a commonly used open source library that existed years before that covered 90% of the functionality.
The Google staff just don’t think to look outside Google (after if Google hasn’t solved it no chance outsiders have) and so wrote something entirely from scratch.
Then normally within 6 months the open source library has added the killer new feature. The Google library only persists because people hold FAANG as great “Its by Google so it must be good!” Yet it normally has serious issues/limitations.
The Google libraries that actually suceeded weren’t owned by Google (E.g. Yahoo wrote Hadoop, Kubernetes got spun away from Google control, etc…).
Every big company suffers from “not invented here” syndrome. It’s not always just because of arrogance. For example, as an engineer at Google, it can be less hassle to use a first-party library than a third-party one.
Also your list of examples is pretty bad. Guava is one I remember filling a real need when I worked at a small Java shop, and as I recall there was no widely used alternative to Protobuf when it came out. Gradle isn’t even from Google at all!
I actually researched my list, most the technologies were used internally for years and either publically released after better public alternatives had been adopted or it seems buzz reached me years after Google’s first release. So I am wrong.
Between 2012-2015 I used to consult on Apache Ivy projects (ideally moving them to Maven and purging the insanity people had written). As a result I would get called in when projects had dependency issues.
The biggest culprits were Guava/GSon, projects would often choose to use them (because Google) and then would discover a bug that had been fixed in a later patch release (e.g. they used 2.2.1 and 2.2.2 had the fix). However the reason they used 2.2.1 was because a library they needed did. Bumping up the version usually caused things to break.
The standard solution was to ask’why’ they needed Guava/GSon and everytime you would find they are usually some function found in one of the Apache Commons libraries. So I would pull down the commons library rewrite the bit (often they worked identically)
Fun side note in 2016-2017 I got called to consult on a lot of Gradle projects to fix the same kind of convoluted bespoke things people did with Apache Ivy. Ivy knew the Gradle ‘feautres’ were a massive headache in 2012 and told you to use Maven for those reasons. Ce La vie.
We tried using Protobuf in 2008 and it was worse than the Apache Axis for JSON conversion (which feels too harsh to say), similarly I had been using AMQP or Kafka for years and tried gRPC when it was released (google say 2016 but I am sure we tried in 2014) and it was worse in every metric I still don’t understand why it exists.
I was using Vaadin in 2011 and honestly thought GWT was released in 2012. I had to use it in 2014 and the workflow, compile time and look of GWT is just worse than Vaadin.