If you're reading this thinking "wow, a recall! tesla must suck at building cars!" then you probably don't know anything about how the automotive industry works and you should refrain from commenting
The problem that occurs in practice is “focus on finishing” leads people to finish without actually doing anything meaningful. Advisors may or may not encourage this depending on where they are in their career.
When you get on the industry job market nobody cares if it took you 3 years or 7 years to do the work, they only care if it’s meaningful.
If you can somehow get your hands on a dozen NVL72 racks and duct tape them together in such a way to rent them out as a service, you can make your money back in less than 2 years at current demand pricing. $50M is more than enough to get this going.
It’s hard to argue against hiring contributors, but a bounty system that pays pennies vs. market value for skilled developers shouldn’t be the only interview path, it’s borderline exploitative.
The leap is not really there yet and it's cheap because you are the product. The robot will be a massive headache, will work poorly for most tasks, frequently break and require maintenance. In exchange for $500/mo and providing those test hours in a novel environment and the data that goes with it, you get to have a robot in your house that occasionally does something right. The bet being made here is that they can turn that data hose into a useful robot before this poor customer experience tanks their brand.
Why is a centralized service provider for crypto useful? It doesn't solve any of the problems that banks and credit card companies solve for cash. Those problems are already solved in the decentralized use case.
Okay and the key difference between crypto and cash/credit/whatever is supposedly that it is decentralized. Or have we abandoned that false premise now?
A common refrain here seems to be that there is no good std lib, which makes sense for something like "chalk" (used for pretty printing?)
That being said, let's take color printing in terminal as an example. In any sane environment how complicated would that package have to be, and how much work would you expect it to take to maintain? To me the answer is "not much" and "basically never." There are pretty-print libraries for OS terminals written in compiled languages from 25 years ago that still work just fine.
So, what else is wrong with javascript dev where something as simple as coloring console text has 32 releases and 58 github contributors?
As an outsider to the npm ecosystem, reading this list of packages is astonishing. Why do js people import someone else's npm module for every little trivial thing?