From that article: "As Dogen puts it, they’re effectively “scraping by,” in part because they’re still living “paycheck-to-paycheck,” despite their generous salaries."
That's right: they're each making $250K/yr, and living paycheck-to-paycheck as they describe it.
In my opinion the addiction cost likely outweighs the benefit in this particular example, especially since there are so many other less addictive ways to get inspiration for art.
It is however, interesting to me to confirm they are aware of other AVs and can sync with them, enable better safety, and potentially could optimize routing through traffic with the combined data. Imagine if the car in front could warn the car behind of an incident, enabling it to take action before a human driver would even be aware of the incident.
> Imagine if the car in front could warn the car behind of an incident
They can, that is why cars have all this pretty lights in the back! They can warn of several things, like intention of turning, braking, accidents, is amazing.
And it works wonders if the human driver focus on the trafic ahead of the car just in front
Yeah, the lights in the back of your car can warn of exactly four things:
- The car is going to turn left (one blinking yellow light)
- The car is going to turn right (one blinking yellow light)
- The car is stopping (three solid red lights)
- An unspecified error occurred (two blinking yellow lights).
It's not exactly a high - bandwidth form of communication. Most of the purpose of the lights behind your car is to remind other human drivers of your continued existence. As you point out, some of this deficiency can be made up by not looking at them.
Imagine a world where you could automatically talk over an intercom with the driver in front of you about traffic conditions. I bet you'd find safer, better-informed driving. Self-driving cars make that theoretically easy and humanly pleasant.
My main gripe with this article, is it mentions that their product was born as a result of a "painful expensive experience" of not creating a "Pricing Engine", but they don't at all elaborate on what that experience was.
I want to know what problems that they built this to solve specifically, so that I can foresee future problems that I may run into. But they don't elaborate at all, and instead just mention that their product solves those unmentioned problems.
That’s fair. Having dealt with this myself, I’m very familiar with the pain involved, as I’d imagine most developers/entrepreneurs who have had to implement billing and then iterate on pricing are. It gets messy really fast.
Perhaps they’re more targeting people like me who have experienced this issue and don’t really need it explained, but I agree going into more detail on the specific challenges is probably a good idea to appeal to a wider audience.
ASL recognition is an insanely difficult problem to solve because it requires solving hand, finger, and arm pose estimation with occlusion, which hasn't even been properly solved in VR, let alone through webcams.
I program in my head, and yes, I often do see the code in my head. In some sense, it's like a spatial experience, where each file is a different "room", and those rooms have contents of the code.
When I imagine programming something, I make mental plans of what code goes in specific rooms (Files, or directories), and what that code will roughly look like - At first a rough shape, of a class with particular methods, and over time that resolves into more and more detail such as what the methods will do and how they will interact with other parts.
My memory is really bad though, so if I try to come back to this a week later I will have forgotten the whole thing unless I make very detailed notes.
How?..