Given the well-known problems with Tesla's Autopilot and (not even close) Full Self Driving, I wonder how many Tesla accidents occurred as a result of driver inattention.
Unfortunately, the study just counted accidents and did not look into what kinds of accidents occurred. It would be fantastic to be able to conduct further research.
Like with anything publicly traded, the price of a share is principally derived from belief. Much of this belief comes from a person projecting where the price will be in the future. With Tesla, many people and institutions projected that that price would increase in the future. Now many of them do not.
Belief in the direction of the price can come from examining the financial fundamentals of a company and the perceived value that it may increasingly generate ("fundamental analysis'). Or it can be speculative, where people believe other people will buy (or sell) more based on observed buying/selling activity ("technical analysis").
With Tesla, many investors were using their own version of technical analysis that far surpassed the valuation that a reasonable fundamental analysis would have derived and even derive today. There was and is a mania, much like there has been and there is for many forms of cryptocurrency.
The recently declining price is likely due to a collective perception that Tesla has been overpriced and, due to recent factors, that the fundamentals that justify the pricing for a share will diverge even further from its recent pricing. From a fundamental level, Tesla was unlikely to justify its recent pricing. An irony is that the earlier mania was so intense even today, after such a pronounced plunge from the start of the year, it likely remains seriously overvalued.
It's unlikely that the rate of improvement, however you estimate it, will continue at the same rate. This is a Pareto effect, with marginal gains ever more difficult to obtain.
And the edge cases FSD can handle will be impaired by the sensors they do (not) install. While they make a good point that sensor fusion can impair comprehension, the removal of radar makes it hard to avoid the edge cases most calamitous.
Blackout curtains. I and I imagine, most people, are sensitive to light. Blackout curtains prevent light from reaching your eyes, resulting in your getting more sleep.
Eyemasks are also effective, but (1) you have to tolerate having something on your face and (2) they can get dislodged while you are sleeping, rendering them ineffective.
Riffing off of BugsJustFindMe's comment, what kind of privacy/security can you offer at this time? I would love to use a tool like Mozart, but I work with data that contains protected health information (PHI). PHI requires a greater degree of privacy. People working with proprietary financial information have similar concerns.
I suspect most people who read HN weren't around when this movie came out, but I was around then.
There was tremendous hype -- the excitement that this film generated led to lines of people waiting outside movie theaters just to get their chance to see it. People would watch it and then get back into line to watch it again. I remember hearing of people who watched it 15, 20, 25 times.
Star Wars substantially advanced special effects. If you want to get an idea of what the state of special effects were in that era, watch Star Trek (the original series).
"Star Wars" felt _real_. Lightsabers, the use of a "Force" where you could physically moves things from a distance, the glissando effect when a starship goes into hyperspace-- these were all incredibly credible and mind-blowing to people back then.
Star Wars didn't just live up to its hype-- it has exceeded it, becoming a fixture in American culture, and becoming a franchise that continues to generate interest and income today.
Please spare us from reports of studies with few subjects (n < 50), based on subjective self-report, and with results reported that were unintended by the study's design.
It's just p-hacking or random chance and a news outlet's way of generating clicks for itself. These findings are made public, and then almost always quietly disappear into the churn of other scientific ideas of dubious validity.
If only the follow-up, larger (n >> 50) study that later is conducted that reports negative results was as widely reported and disseminated.
Ah, the 1970s and 1980s. Imagine a world with no cell phones or Internet. How are you going to get your debugging help now? StackOverflow doesn't exist.
To add to this list:
- Manuals. Reading carefully through the documentation was necessary for mastery. Both hardware and software. These were often closely associated-- you couldn't always just concentrate on one and abstract away the other.
The step counting seems to work reasonably well. At least, it's internally consistent. The same workout or same route done multiple times results in no more than 5% variation when counting steps.
But the sleep tracking has been awful. A lot of days I'll get up, sit in a chair, and will surf the web for several minutes, say 45 minutes, and the watch inevitably records this time as also sleep. It's quite ridiculous and the software doesn't allow you to edit the log with the correct time. You can only delete entries, not edit them.
I've found my Samsung Galaxy Watch Active2 to be hilariously incorrect with estimating sleep tracking, and I miss my Fitbits for getting that measurement.
Example: on Sunday, I woke up, drove 20 minutes to a trailhead, proceeded to strenuously hike for an hour, drove 20 minutes back. When I checked the sleep log later that day, the watch had automatically assumed I had been sleeping through the entire hike.
I like most other things about this watch, but sleep tracking is not one of them.
Perhaps there is a little competition component, but the idea is to stay longer in the ketosis state. If you're doing 18/6, then your body will be in a fasting state for a longer time, and the belief is that the longer your body is in that state, the more benefit you will reap.
It feels wholesome and healthy to point to WeWork as a thinly-veiled re-packaging of office space and an illustrative example of what's not a "tech" company. With the collapse of their IPO, people are piling on heaps of schadenfreude.
But I can't help but wonder: how much of this is envy? Who wouldn't want to be perceived as inspirational and forward-thinking when seeking support for a pet business endeavor?
The choice of which words to use to market your idea, the value of being able to recruit people to fulfill the idea, the ability to persuade people to fund your idea. Isn't there some value provided by inspirational leadership?
Neumann may have duped a credulous Son, but he put WeWork in the position where it received Son's consideration.
I'm not excusing the grifting and self-enriching.
At the same time, I've seen situations where the charisma and the resolute determination of a leader makes a huge difference in how the team executes. WeWork may be a glaring example of what not to do, but it's also an example of the value of politicking-- of agilely positioning your endeavor to receive investment, both monetary and emotional.
I will respond only to Q1, taking the perspective of analytics and data science.
Answer: PostgreSQL > MySQL
Postgres implementation of SQL includes a few useful clauses that are useful for analytics that MySQL does not support.
It used to be that MySQL had no window functions, and that made it wholly inferior to Postgres when it came to analytics. However, it seems MySQL began supporting window functions two years ago, so that is no longer a reason to choose one over the other.
There are at least two features supported in Postgres that are not available in MySQL that I use often enough to care:
• SELECT DISTINCT ON
• FULL OUTER JOIN
Having these saves dev time. It is possible to implement either using MySQL, but your code will be more verbose, creating more opportunities for error.
If you care about analyzing the data for data-scientific purposes, you would be better off using Postgres. It isn't just the couple of extra clauses. It's also having more (useful) indexing choices and little choices like being able to use two pipes (||) to concatenate strings instead of CONCAT().
We're Uniform Teeth — the first premium, clinically credible consumer brand in orthodontics. We're making orthodontics cheaper, faster, and more accessible for everyone, plus we're backed by the same investors as Warby, Instacart, Casper and GoodRx. Read about us in TechCrunch.
## The Environment
Fast-growing startup, small engineering team (~4 members right now), more greenfield than legacy code
## The Role
You love React. We love React. You’ll work on every aspect of the business, creating a superb experience for our customers.
## Responsibilities:
• Build features on our react native app (non-native code), EMR and lab tool
• Integrate real-time integration with our API via websockets
• Maintain (and improve) code quality, test coverage, and engineering acumen
• Work with product, clinical, and our engineering team to define specs and dictate how features will be build
Feel free to email me at jerry [at] uniformteeth.com if you intend to apply— happy to answer any questions you may have.
We’re also recruiting several positions not specific to tech, for onsite in SF: clinic managers, sales managers, orthodontic assistants, lab technicians, packaging and shipping specialists, CAD/CAM dental technicians.
Uniform Teeth is a fast growing startup making high-quality orthodontic care more affordable for everyone. Our main focus currently is straightening teeth by using clear aligners.
Uniform Teeth's competitive advantages in this market: (1) a focus on one service, allowing for optimization of every aspect of the business (marketing, operations, manufacturing, and clinical care); (2) shorter treatment times; (3) lower prices; (4) ability to handle complex cases; (5) single-minded devotion to customer service and excellent dental care. Check out our reviews [0].
We’re looking for a full stack engineer to join the Engineering team. This team builds functionality for our customers (patients), clinicians, support team, and manufacturing. Looking for primarily onsite, allowing for a fair degree of remote work once you grok the codebase.
For more information, including how to apply, please visit our Careers page at https://www.uniformteeth.com/careers/ . Please email me at jerry(at)u------t----.com if you intend to apply— I’d be happy to answer any questions you may have.
We’re also recruiting several positions not specific to tech, for onsite in SF: clinic manager, sales manager, orthodontic assistant, lab technician, packaging and shipping specialist, CAD/CAM dental technician.
Uniform Teeth is a fast growing startup making high-quality orthodontic care more affordable for everyone. Our main focus currently is straightening teeth by using clear aligners.
Uniform Teeth's competitive advantages in this market: (1) a focus on one service, allowing for optimization of every aspect of the business (marketing, operations, manufacturing, and clinical care); (2) shorter treatment times; (3) lower prices; (4) ability to handle complex cases; (5) single-minded devotion to customer service and excellent dental care. Check out our reviews [0].
We’re looking for a full stack engineer to join the Engineering team. This team builds functionality for our customers (patients), clinicians, support team, and manufacturing. Looking for primarily onsite, allowing for a fair degree of remote work once you grok the codebase.
For more information, including how to apply, please visit our Careers page at https://www.uniformteeth.com/careers/ . Please email me at jerry [at] uniformteeth.com if you intend to apply— happy to answer any questions you may have.
We’re also recruiting several positions not specific to tech, for onsite in SF: clinic manager, sales manager, orthodontic assistant, lab technician, packaging and shipping specialist, CAD/CAM dental technician.
Unfortunately, the study just counted accidents and did not look into what kinds of accidents occurred. It would be fantastic to be able to conduct further research.