3 ms·
Its so weird to me that they'd do 99% of the effort and just skip past the 1% of work to provide a dumbed-down summary and instructions for broader appeal. Clea
by tmpz22 3y ago
Its so weird to me that they'd do 99% of the effort and just skip past the 1% of work to provide a dumbed-down summary and instructions for broader appeal. Clearly these are released in part for public-relations and industry clout.
Don't get me wrong they published this, it took a ton of work, they didn't have to do it. But its ultimately a form of gatekeeping that seems to come straight out of Academia. And honestly, that part of Academia sucks.
- sdenton4 3y agoA good research team is a handful of people working on a focused set of questions. A good product team is probably around a dozen people minimum? Especially if you need to hit the quality bar expected of a release from a BigCorp. You've got frontend, UX, and server components to design, in addition to the research part of the project. The last real app I worked on also included an app backend (ie, local db and web API access, separate from the display+UX logic) and product team. Oh yeah, also testing+qa, logging, and data analysis. And after all that investment, God help you if you ever decide the headcount costs more than keeping the lights on, and you discontinue the project... Public app releases are incredibly expensive, in other words, and throwing a model on GitHub is cheap.
- o1y32 3y agoIt's not 1% of the work. If you have ever written public documentation, or half-decent internal documentation that is understandable to people outside your team, you would know that it takes a lot of effort to get it right. Let alone something highly technical like this. If you get things wrong or skip things you think are trivial but not to others, you get more questions. And it is not a one-time thing, it is a living document that needs to be updated and revised over time.