790 karma · joined February 21, 2013
Also by being high end, theres opportunity to be very different. These stations shouldn't even look like traditional stations. They could provide services that appeal to affluent markets and provide good profit margin. This will be necessary at first because raising gas price alone won't be enough to cover costs.
I think the only viable option for them is Lyft Line/Uber Pool. It benefits from network effects (more using the service, better it gets) which also prevents newcomers. It could become a monopoly like Facebook. They should be pushing this harder than unrealistic dreams of level 5 self driving.
This is how organic food started with Whole Foods. And the same strategy could work here.
The key factor is to consider which senses are optimal UI for each device. Smartphones dominate the visual and audio senses. Smartwatch simply can't compete there. So smartwatch should have a very simple very low power display like the Fitbit and Pebble and maybe a simple speaker/mic.
So what sense is the smartwatch good for? It's touch. There is a lot of potential of using vibrations/touch as a UI. For example, I think the Apple watch vibrates for turns when you do a Maps route. That's a good start. They need to focus more on things like this. There's a lot you can communicate with vibration, kind of like morse code (such as two quick vibrates, a long vibrate, etc.)
And now Apple has a very advanced touch sensor (the new one in iphone 7). Get rid of that silly big screen on Apple watch. Put the touch sensor there. Why not just allow thumbprint scan, wave my watch at a Apple Pay terminal, and buy things? Way less effort than taking out my phone.
These kind of pure touch and vibration UI is a huge open field. And I think Apple somewhat understands this. But they need to make the big step of dropping that screen. Because that's not where the smartwatch is strong. And it would also allow long battery life which is more important for smartwatch. People are used to daily charge for phones. But much less tolerant of that for watches.
It's actually not a bad system for fresh graduates. If they studied hard in college, all that DS and algorithm knowledge should still be fresh. And it's away to see who studied in college and who didn't. But it's only useful here because there's nothing else to look at for fresh graduates, they have no experience.
However, it's a very bad process for senior engineers. Google should have a different process for seniors, but they probably don't care enough to change.
Then I get to the last line. Open office, has video games, happy hours, other typical things designed to attract those in their 20s. It's all a hidden message screaming, if you're old, don't apply. And they want someone with 8+ years experience! It's ridiculous.
LA Metro opened up the Expo Line, a light rail between downtown LA and Santa Monica, in May as part of its effort to wean people off car ownership. When it began running, Uber ran a promotion for $5 off Pool rides to or from Expo line stations. For ride-hail companies, partnering with public transportation agencies to market themselves as companion services can increase mutual ridership. Kan, Lyft’s LA general manager, said three of the top 10 destinations for Lyft rides are metro stations.
If this trend continues and becomes more common, it has potential to really change transportation in LA. LA Metro is working on expanding the rail lines but there's always the "last mile" problem (not literally 1 mile, but usually last few miles to get/from rail station to destination). UberPool/Lyft Line can be the solution for this and the more people use it, the better solution it becomes.
- Long remote: When someone is offshore or many time zones away (such as India or Eastern Europe).
- TZ remote: Same timezone, but requires airplane flight to meet.
- Local remote: Within driving distance.
Local remote is the best of both worlds and all companies should be doing this. It can be a 3-2 balance (3 days remote, 2 days in office) or 4-1, whatever makes sense for the team and company. Employees get the benefit of remote (flexibility, no commute) and in person meetings (such as designing a new system on a whiteboard). It's sad that so many tech companies (such as Google and FB) don't do this. Considering that it's tech that allows this (with video conferencing, git, slack, etc.), it's ironic that tech companies are so resistant to doing local remote.
TZ remote can work, but it should be only for employees who are already established at the company (spent many years doing local remote). The connections developed during the local remote years will help make TZ remote work. And they can fly to the office a few times during the year to refresh those connections.
Long remote has a lot of issues. The big time zone difference, lack of any history of in-person meetings, and culture differences make it very difficult for this to work.
EDIT: The more I think about it, this is such a good idea I hope Lyft is seriously working on this. With something like Lyft Line, the optimization potential is immense. Assuming each Lyft Line car can have 3 passengers and most workplaces would be within 2-3 miles of a rail station, rides could be very cheap and fast. For example, most coworkers going home would probably share the same Lyft back to the station. The short distance (assuming a 2-3 mile radius) combined with Lyft Line would allow very high throughput during rush hours. If the Lyft cost can benefit from the commuter tax deduction, that's just icing on the cake since the car sharing alone should drop costs by a lot. And there's also networking effect. Coworkers will want to encourage coworkers to do this so they can lower costs for everyone.
The solution is to avoid these companies. There's a huge world outside SV. These may be known as "boring" (banks, insurance, etc.) but they will not have the stupid ageist algorithm games known as "technical programming interviews". And they respect experience. And they won't have an ageist culture, it will be ok to go home early and be with family.
1) Focus on perfecting low speed bumper-to-bumper traffic fully autonomous driving on freeways.
2) Focus on passing legislation to allow zero driver liability and awareness when using the low speed bumper-to-bumper traffic self-driving mode.
The speeds are low and so the risk factor is reduced by orders of magnitude. Even if an accident happens, it won't be fatal because of the low speeds. And that should also help with the legislation issues. Also, this feature would be very popular. Imagine a commercial with typical bumper-to-bumper traffic. Then the camera zooms in and the driver is sleeping. When the car detects that bumper-to-bumper traffic is going to end soon, it triggers a loud alert which wakes the driver.
And yet all the car companies are ignoring this. I remember reading about early lane keeping and automatic speed cruise control and it would not activate under slow speeds. I was incredulous when I read it. They made this not work for exactly the most useful scenario? I don't care about self-driving for road trips, they don't happen often. And door-to-door self driving is the ultimate goal, but it's going to take a long time to get there. But helping to alleviate the horrible bumper-to-bumper driving by allowing drivers to do something else can be done with current technology. The whole self-driving effort feels like no one has done any market research to see how to make it help with real world situations.
1) How to clean data. Real world data is always dirty. It mixes strings and ints, has commas and quotes where they shouldn't be, etc. Knowing how to think of data in terms of a standard format and having a plan for exceptions is very important.
2) How to manipulate data. Python, JS, or some other simple dynamic language. Teach how to do functional style programming such as list.forEach(<lambda>) to transform or analyze data.
It's easy to make homework and tests for something like this. And these are fundamental skills. It doesn't matter if Python or JS fades away. It doesn't matter if popular formats change from JSON to something else. It's about teaching how to think about data and how to get it in a form where it's easy and reliable to do analysis or transformations with it.
We don't need to make programming "fun". We need to treat it like algebra. A basic skill that all should learn. But that doesn't mean making web pages or mobile apps. And it also doesn't mean the theory focused CS topics like data structures and algorithms. Just start with learning how to think of data in a standard form like CSV or JSON. And how to use a programming language like JS/Python to do something with the data. After students master these skills, it can be integrated into science classes. Students will know how to write simple scripts to clean up the data from a lab test and analyze it.
The reasoning for this seems intuitive and correct. But I'm wondering if there's evidence it's wrong. What are these great companies for developers and are they software revenue companies? If not, what are the forces that maintain a good workplace for developers when software is not the main revenue?
1) Fossil fuels costs will eventually start rising and never come down again. How much investment and attention will synthetic production receive when oil is $100/barrel? Or at $200/barrel, or $300/barrel? More investment could lead to significant process improvements.
2) Solar energy has improved tremendously and continues to improve more. But the great weakness of solar is that it's only effective at daytime. Anything produced in excess of daytime demand is basically waste energy. Since it's waste energy, the inefficiency of the oil synthesis process doesn't matter. The only competitor here is other energy storage methods such as batteries. The key question here will be, is it better to store this excess waste energy in batteries or use the synthetic process to make oil? From a pure efficiency standpoint, battery is better. But when considering the existing oil infrastructure, the answer is not as clear.
https://en.wikipedia.org/wiki/E-diesel
The inputs to this are just energy + water + CO2 = oil. No corn or other plants required. Currently this type of technology is far from cost competitive. But that could potentially change if more was invested into this area.
But we live in an oil world. There are billions of cars out there. Cars are big investments that are handed down generation to generation like houses, especially in developing countries. EV car sales are still a drop in the bucket compared to ICE car sales.
If we want fast and rapid action on climate change, the quickest path is not pushing EV. It would be massive investment in reducing the cost to make synthetic oil. This may seem impossible, but that's what many said about solar competing with fossil fuels. EV car enthusiasts often talk about how EV cars get immediate environmental benefits from power plant upgrades such as burning coal to solar. But how much more orders of magnitude environment improvement would we get from carbon neutral oil creation? If a cost effective way was found that could compete with fossil fuels, billions of cars would immediately benefit environmentally.
Again, another computer analogy. Imagine someone invented a beautiful new elegant programming language that reduces CPU energy use by 50%. At the same time, someone found a way to reduce JVM CPU energy use by 20%. If we wanted the shortest path to worldwide energy reduction in CPU, what would be faster, just update the JVM for millions of servers or rewrite everything in the new programming language?
The big issues with oil are due to the source, not the technology itself. Right now the source is underground carbon sinks (fossil fuels). But what if we produced synthetic oil using excess solar energy during daytime? It would pull carbon from the air. And would burn cleaner than any fossil fuel source.
It seems many dream of a battery future. But is it really better to produce millions of batteries instead of just finding better ways to make oil?
It kind of reminds me of the classic desktop app vs web app debate. One big advantage of web app is that upgrages are single source, just update the server. But desktop apps, there may be many multiple old versions out there because users don't always update. In a similar way, why are we focusing on the very difficult and slow task of upgrading all cars to EV? Why not improve the source of oil itself?
1) It has the same strong CA protection against non-competes as Bay Area.
2) Starting to develop some big and significant "anchor" tech companies such as Snapchat.
3) Surrounded by good universities (UCLA, USC, Caltech)
4) Main tech hubs are Santa Monica and DTLA. These will soon be connected by a new rail line (opening this month)
5) Housing is expensive, but not as bad as Bay Area. And rail line should greatly expand cheaper housing options while being able to work at a tech hub.