Just because open source models are almost as good, doesn't mean you can underestimate the convenience factor.
Both can be true: we're in an AI bubble, and the large incumbents will capture most of the value/be difficult to unseat.
IIUC, author is a Staff SWE, so this tracks.
See also "Worse is better" which has been debated a million times by now.
Blog post for the paper: https://waymo.com/blog/2022/12/waymos-collision-avoidance-te...
If something is built to last 10 years, it makes it likelier that it can survive another 10.
Then on the first page of the "silly little book," where I already have the question: "why should I read this? Why would an employee spend time reading this?" Immediately he addresses that: "if you read this book and pass a quiz I’ll give you $1,000." And if you've seen MrBeast videos, it's not inconceivable that everyone who's read the manual has actually received $1,000.
Corporate leaders would do well to learn from just this. What are you saying in the all-hands meeting that takes 1,000 SWE-hours that's actually worth that much? What value does your employee handbook/documentation provide (in my experience, a lot of documentation provides negative value by virtue of being so out-of-date, confusing, or just wrong).
Jimmy has probably done the math (in a intuitive sense; I don't think he has strong math skills), and it's worth the employee-hours for him to pay them $1,000 to read this PDF to avoid having them waste time or make mistakes they've already made. It's probably worth a lot more than $1,000.
Context: I'm a software engineer at a growing company. We're (hopefully) going from a startup into a real revenue-generating service.Along with this comes the usual growing pains. Code quality deteriorated a bit with how hard we were pushing for certain milestones.So now, we have engineering excellence talks to go over topics that might be useful for us engineers as we scale and increase code...
What can we do about it? Is trying to out-lobby i.e. regulate the CC companies the only way? I noticed that other countries don't seem to have this problem.
(Not saying anyone "deserves" that or that's how it should be, but that's just how it is here in the valley.)
Those art things require training just like any other profession.
Feedback: maybe add a feedback section to the site? Haha. Dissect is spelled with 2 S's, and there's a broken link at the end of the virtualenv section.
Thanks for your work! Learned a few things for sure.
Thanks. Nit-picking again, but drinking the Kool-Aid does mean "unquestioning, ... without criticism" implying that those who are drinking wouldn't have such reservations. That's what I was confused about. Oh well. Language is evolving, what else is new.
And it seems like you mean exactly the opposite of what you've said, based on that definition - you're not drinking the React Kool-Aid, or drinking the anti-React Kool-Aid.
I'm not trying to impose grammar OCD on anyone by any means. Like I implied, I'm probably one of the more ignorant people about these phrases. I just think it's confusing when people say things like "could care less" and "drinking Kool-Aid" when they actually mean the complete opposite. It's very bizarre to me but OTOH I guess it's fascinating that English is just that flexible.
This course reminds me a lot of the Berkeley course posted a month ago, if anyone wants to see the discussion there: https://news.ycombinator.com/item?id=9838196. From what I can tell, the coverage is almost the same, except that the Berkeley course pretty much trades computer architecture for declarative programming and some other briefly-covered topics like machine learning, map reduce, concurrency, etc.
It may or may not be the same to parse, say, JSON and XML.
But how is
xmlDoc=new DOMParser().parseFromString(booksXml);
newatt=xmlDoc.createAttribute("edition");
newatt.nodeValue="first";
x=xmlDoc.getElementsByTagName("title");
x[0].setAttributeNode(newatt);
as easy to use as
JSON.parse(booksJson).title.edition = 'first'
?