1,751 karma · joined January 31, 2012
Previously: Growth Engineer @ Uber Product Engineer @ BitTorrent Full-stack Dev @ ZeroCater Game Engine Programmer @ Terminal Reality
Email: d@nielpie.rs Twitter: danielpiers Github: dpiers Blog: http://da.nielpie.rs Resume: http://goodwith.computer
I can’t believe Tesla has gotten away with selling a feature that doesn’t exist, and will never be delivered, on so many cars for so long. Tesla began selling “full self-driving” in October, 2016 and a month later marketed it with (now known to be heavily controlled) video of a car driving itself for two minutes. Owners of those initial cars have probably paid them off by now and still don’t have a feature they were sold.
The devpod flow is a lot smoother. I had my laptop replaced recently and was up it running again in an amount of time that felt like cheating.
How was this ever going to end any other way? Imagine how preposterous the idea of storing $650mm in USD in a random game studio's checking account would be.
I'm using a bunch of used drives and not worried about disk failure because worst case scenario is replacing the drive and re-generating new plots.
In this case it seems the patent is still available for anyone to license[2]. They have special licensing terms for startups that are pretty favorable[3].
1: https://www.federalregister.gov/documents/search?conditions%...
If you add in the fact that these exchanges allow trading on margin, you could have a situation where people are forced to liquidate their holdings regardless of the current price. It's the perfect storm for a flash crash.
I intended to call out the folly of their idealism - "the war cannot be won" - the Feds don't have to win a war. Every battle they win destroys the lives of the people foolish enough to be involved. Once you're in their sights it's only a matter of time before you slip up and then you're done.
You talk a big game, but I don't think you understand the reality for people who are involved and get caught. Let me know when one of your closest friends gets arrested by the Feds and you don't get to see them for a decade plus.
This would be useful for anyone who uses it to block out traffic/street noise at night.
Bandwidth is the biggest problem small restaurants have in managing a delivery service. If you don't have enough drivers to meet peak demand, you have to either decline orders or make customers mad when their order takes >1 hour to arrive (and disgruntled customers don't typically re-order or tip well). If you have too many drivers, they are making less in tips and you are probably spending more to bring their tipped wage up to minimum wage - and if it happens often they are going to quit.
I remember my dad disconnecting the phone at the store when they got too may orders to handle. We ended up using my mom and siblings as the flex/surge delivery capacity. If delivery apps had existed at the time, he would have gladly traded the headache of employing drivers and managing capacity for the ability to make and sell as many sandwiches as he could. In todays' world, if he got 12 orders going to different parts of town at the same time, he could accept all of them and know that if he could make the food, someone would be able to deliver it.
Delivery networks also increase courier efficiency by adding the ability to batch deliveries from multiple restaurants and avoiding the need to round-trip every order back to the restaurant when you are done. Couriers on Eats/DD can drop off one meal and be dispatched another from a restaurant nearby, and don't need multiple people who live near each other to order from the same restaurant at the same time in order to have efficiently batched trips.
There are efficiencies in the network model that can't easily be replicated by individual restaurants with their own drivers. The gold standard is Dominos but they are a behemoth that can't compare to any other restaurant - they are singlehandedly as large as Doordash.
If manufacturers lose their substantial licensing fees, they would be forced to charge more upfront for the consoles which is objectively worse for consumers.
Most devices are connected to HomeKit through a Pi running Homebridge. I wanted voice control and Apple is the company I distrust the least since they at least pretend to care about privacy.
I have only messed around a little with HomeAssistant, but that's what I would recommend if you want entirely locally controlled home automation. They even have a voice assistant[1] but for now it's worse than Siri, which is really saying something.
1: https://github.com/SwiCago/HeatPump 2: https://www.thingiverse.com/thing:2392856 3: https://www.home-assistant.io/blog/2019/11/20/privacy-focuse...
I don't think most people comprehend what their devices are doing, or how their data could be used against them. My robovac has a LIDAR sensor that maps the house - that's cool - what isn't cool is that by default it uploads those maps to Xiaomi and they can connect it via GeoIP (or GPS if I ever use their app) and have the location and floorplan of my home. I'm not special enough for that information to be very valuable, but it's still super creepy and I would prefer they not have it.
It was horrible and fantastic at the same time. The debugging tools were poor, most of the documentation hadn't been translated to english yet, and testing the dual-camera rendering pipeline required hunching over the desk to be in the sweet spot for the parallax to work.
I still love that kind of low-level development, but these days python and shell scripts pay the bills. RIP 3DS, and thanks for the memories.
1: https://www.engadget.com/2010-05-17-is-this-a-prototype-of-t...
The big differentiator is that phones have become the most frequently used personal computing device for many people, and we expect the freedom to use it how we want.
It is not considered harmful to have a beer while breastfeeding. I'm sure the subject of the photo was aware of how it would be perceived and didn't put her drink out of frame to help normalize public breastfeeding.
As we decelerated to make the turn, I realized we might not make the light and had to decide whether to take the turn at an aggressive speed or heavily brake to a stop. Suddenly stopping would pose a significant risk to the passengers in my vehicle and in the vehicle behind me. I observed that the intersection was clear and committed to the turn.
This is the exact 'dilemma zone' described by Mats. If you are still having a hard time picturing it, there are plenty of diagrams in the ITE journal article that explains his calculations.
I just received a citation for making a right turn at a red light 0.3 seconds after the light turned red. I had already been preparing my arguments for why my actions produced the safest possible outcome, but these materials should prove exceptionally useful in our case.
Eventually time gets the better of us all. I don't think that's an insensitive statement, just pragmatic/realistic.
80+ years old: 14.8%
70-79 years old: 8.0%
60-69 years old: 3.6%
50-59 years old: 1.3%
40-49 years old: 0.4%
30-39 years old: 0.2%
20-29 years old: 0.2%
10-19 years old: 0.2%
0-9 years old: no fatalities
I think most people are blowing it out of proportion. It's just a bad flu, and it seems to be responding well to remdesivir treatments in early trials. I also think that, with the news we're getting now about asymptomatic/minor cases, it's highly likely the real number of infections is much larger, which would mean the CFR numbers are way too high.