Another Group of Google Veterans Starts a Self-Driving Technology Company
bloomberg.com
bloomberg.com
If the difference was more subtle such as 2 to 3 times X, then the incentive to go through this much trouble to retain much of the value you create is much smaller.
I would summarize this effect as BigCorp HR being much more disciplined/constrained on individual compensation than the M&A department. Naturally, well-positioned and clever employees will capitalize on this.
Google was already at the center of the high-tech employee wage-fixing earlier this decade, so filing lawsuits to create deterrence wouldn't be that surprising.
https://en.wikipedia.org/wiki/High-Tech_Employee_Antitrust_L...
Between these, which do you think is more likely?
Or, CEOs don't have the same set of options engineers have, or, CEOs are drawn from a pool with different preferences than engineers have, or...
Well, lots of other reasons your dismissal of the claim about engineers based on CEO behavior is unconvincing.
Learn everything.
I have a goal, it is to be better than average at every "skill".
Plus, yes, there are other goals than "not working".
I expect a startup was the only option to execute on the idea with a decent level of autonomy. Google/Alphabet already have well established teams in the areas of mapping & autonomous driving so you can't just go ahead and start your own multi-engineer effort.
We saw this with the Nest folks, which was really a shell company that hired as many talented folks from Apple as possible, built a product, and then put themselves up for sale in the valley: either back to Apple or to Google.
This basically makes joining one of these startups a no-risk opportunity: huge upside if the thing you build actually works out, slide into a bigco job again if it doesn't...
I've always thought it would be a great (albeit risky) way for someone who is talented but stuck in a go-nowhere job to get a nice bonus and/or raise:
1. Quit your job doing X
2. Found a company to do some related Y
3. A year layer or so, get purchased by your old company for the technology.
It's also an alternative way to get a new job somewhere where you can't seem to get through the interview funnel. I'd imagine that at some Silicon Valley companies it's easier to get acquired than get hired.
I think the biggest argument here is that sometimes the end goal becomes not the work that person is currently doing but the payout down the road if their actions line up in a certain way. If your goal at Google is to leave in three years and start a self driving car-company to get acqui-hired, you might for instance spend three years making lists of people to take with you or knowledge that won't violate NDAs or whatever. Though often times that might be acceptable, a.k.a. the 'you don't owe your employer anything' line of logic (which generally I agree with), sometimes it can become morally dubious if for example, it corrupts personal relationships or becomes manipulative.
And then finally you get the case of the Waymo guy who may have planned and conspired to steal information on his way out the door, ironically after having already gained multi-generational wealth.
MobilEye makes sense, they have vested financial reasons that dictate what they do, so they can't turn their back on maps which they've been using for such a long time.
On the other hand, starting a company in maps for self driving cars, especially by what appears to be industry veterans, is far more interesting.
I'd argue also they're using maps in an even more fundamental way - most driving occurs in places where the driver has already been, and relying on a wetware-stored map is a critical part of safe and effective driving.
Local knowledge - traffic patterns, weird traffic signal setups, difficult lane changes, etc, is pretty critical to driving well.
Since I don't use Waze (horrible experience), Google Map won't tell me there's a camera ahead, or police is ahead.
The expectation that self-driving can be perfected without any kind of pre-mapping and the system can behave at high reliably in-situ seems unreasonable. Even humans can't do that.
I don't doubt that 2d maps would be needed like how humans drive with a GPS.
We have a MVP. Google has a MVP, Telsa is a MVP already. I feel we focus too much on building sensors.
First, for a computer to be able to navigate safely on the road the computer needs to be able to recongize and understand its surroundings. Checked.
Next, for computers to be able to be good at driving, we need to train the computer both in the real world and in simulations.
Moreover, to ensure we can optimize route, plan ahead we need data about road condition far ahead of us (and sometimes behind us). To be able to make turns on an intersection safely and swiftly, unlike humans who are terrible at making turns and confusing when to turn, computers can coordinate with one another. This requires good network communication. Bluetooth is weak and unstable. In my earlier example, if an ambulance says it is driving heading my direction, my car can coordinate how to empty up a lane for the ambluance to pass. This level of automation is what one sees in a sci-fi movie, which is really what you want besides being able to avoid obstacles like Bat mobile.
My point is, we should explore how to make traffic data accessible. There is so much one can do with such data. It takes a good amount of time to get the government onboard and help them build such infrastructure. To finish off my point, meter data is not available, right now apps use crowd source to determine whether a parking spot is available or not. Instead of driving around which causes more congestion and sometimes accident, governement should make meter data available, and we can still crowd source by using driver's camera to recongize whether a spot is opened and send back to datastore.
This is essentially the goal of Internet of Things, at rhe city scale. As I mentioned, IBM's SmartCities supposed to do stuff above but I really am not sure if IBM will ever pull off given many of their projects ended up on someoen's desk covering in dust.
For higher precision tragic flow that's going to fail while their is still a high percentage of human drivers. So sure when there are 50+% AI drivers it's a useful optimization. However, for the first decade or so it's not going to happen making it a waste of time for now.
As to finding a parking space, again mostly a non issue for self driving cars, because they don't need to park near people they are better off going to a garage which already tracks open spaces than using street level parking when it's hard to find. Can you slightly optimize this sure, but again it's not a hard problem relative to driving without a person in the car.
But, there's a lot of niches with less competition - yeah, the slice might be smaller, but I'd rather have a 90% chance at 10% of the pie than a 10% chance at 90% of the pie.
I bet whoever capitalizes on this will end up becoming the world's most valuable company. This is a horse-> horseless transformation again.
They said the same about internet shopping way back before the dot com bubble burst. There were hundreds of web-vans, but only one Amazon. I guess everyone thinks of themselves as the Amazon of self driving rather than CueCat[1].
1. I'm embarrassed to say I badly wanted one. http://content.time.com/time/specials/packages/article/0,288...
Has to be fascinating AND deflating if one of your data points was "holy shit we can make $700m in 6 months if we get a team + MVP out the door!".
I realize that non-competes are illegal by CA law, but perhaps they should do the engineering in a different state to stop hemorrhaging talent that tries to compete with them?
The truth is that Google lost this market (or never really had it to begin with). At best they will end up like Microsoft, simply extracting rent via their patent licensing program.
For more information about Route 128 vs Silicon Valley, I cannot recommend the book Regional Advantage by AnnaLee Saxenian enough. It's a bit dated and academic, but it's fascinating if you want to understand why the tech industry in and around Boston lost to Silicon Valley despite having a huge head start.
(2) Even if Google did their engineering in another state, let's say the engineer in question then moves to CA. There's a good chance that CA law would still apply.
Doing engineering in a different state might make it more problematic to attract talent, as might the non-competes separately.
OTOH, maybe Waymo needs to be spun off and be able to offer employees Waymo stock, so it can be a "high-upside startup" option for engineers.