171 karma · joined July 4, 2014
It’s not ready yet, and phase 1 was the really weird stuff. I think Beyond Meat is like phase 2 of “pretty close”. In the near future, you won’t be able to tell the difference
I think you misunderstood the O-ring explanation by citing that idea as an example. It doesn't mean building AI. It applies to any of those fields you mentioned. Good people in field X work together with other good people in field X in top firms -> multiplicative productivity.
In fact, it's probably the area where we see the most gain compared to any other improvements in iPhone versions.
Perhaps your feeling is from the fact that new phones are released in rapid succession. If that's the case, just compare quality in phones a year or two apart instead of a few months.
"In one sentence, how does it work?
Payment Request API enables a user to complete a transaction more easily by reusing information stored in the browser or third party payment apps."
The missing piece is why he doesn't feel pressing criminal charges and suing for IP is an option. The language seems to imply that the answer is for his physical safety. If he's writing this article because he feels safe enough to, then maybe he thinks battling in court requires people to be present and closes the distance safety net.
He's able to list pretty concretely his contributions but is suspiciously vague about the cause of his fear. I'm inclined to believe that it's because he might not think the public would unequivocally agree his fear is sound.
You could point to frameworks which have had majority usage at any given point and say those were the "right" ways at the time. But ideas evolve, which isn't so ridiculous.
" What background knowledge is necessary?
Programming (expected): intermediate Python programming skills: work effectively with loops, control flows, data structures, files, functions and OO programming. Prior experience with PyData libraries is also recommended (e.g. Numpy, Pandas, Matplotlib)Mathematics (recommended): Matrix vector operations and notation.
Machine Learning (recommended): understand how to frame a machine learning problem including how data is represented, how models are evaluated on the task and against each other, and how to optimize model performance for the best evaluation."
Maybe that currently is some parts of the job of an ML engineer. But if that's the only part, I don't think that role should be called one of ML engineer anymore
His slide on "learning to learn" has a goal of removing the ML expert in the equation. Can somebody who's more of an expert in the field comment on how plausible it is? Specifically, in the near future, will we only need ML people who do research, due to the application being so trivial to do once automated?
I'm curious if it's a recruiting strategy he's trying.
I had built this with the intention to sell it on the app store but ended up not wanting to bother with marketing and signing up. But idk, maybe it can garner some buys as a paid developer tool app.
That slogan took multiple passes to grok.
The fact that the word after 'turn' is 're-turn' makes my mind go to the usual purpose of prefixing words with 're': to do again. That's not how it's used here but then in 'repurchases' it is. There's too many twists and turns (no pun intended) from a language standpoint.
That's not the kind of use case that'd require React. I think we're on the same page that for the majority of apps, that setup is overkill. I'm just pointing out that there are apps with complex use cases where the "see where this is going" will end up being more elegant/simpler than fleshing out your own constructs (certainly more than a for loop)
Complexity can be avoided until the number of features reaches some threshold (I don't think there's any debate that it's impossible to avoid complexity entirely if the app is large enough). In those cases, which I think are the majority of use cases, a simple DOM utility like yours would be enough to hide complexity because there wasn't much to begin with.
But some of the websites React powers exceed that feature threshold. For example, if multiple sections of a web app want to update at once, the author could leverage React's lifecycle hooks where needed and rely on its reconciler, but if using a simpler library, might have to explicitly schedule each update in a more hacky/less efficient way.
As a way to bleed it out.
This makes me wonder even more what's wrong with it! I doubt the learning curve is scaring THAT many people away, since employable programmers already demonstrated a willingness to learn hard things. It seems to me that there must be something bad I don't know about the language.