> Your product is not backend-heavy, such as: ...machine-learning models Maybe the meanings of these words have morphed over time, but in what sense is a "machine-learning model" not a back-end concern? It sure as heck isn't front-end... (E.g., the current wiki page for "front and back end" explicitly mentions "converting the symbolic phonetic representation into actual sounds" as an example of a back end concern, an…
> Maybe the meanings of these words have morphed over time, but in what sense is a "machine-learning model" not a back-end concern? It sure as heck isn't front-end... Huh? They're giving it as an example of something that is backend-heavy that they don't want your product to be like. You've got it backwards. > (Your product is (not (backend-heavy, such as: ...machine-learning models)))
I think it's you who have got it backwards.
Here's the entire thing:
"This probably isn’t a good fit if:
Your product is not backend-heavy, such as: an iPhone game, hardware, machine-learning models, blockchain, or embedded systems."
I read that as "if you're a hardware startup, you're not backend-heavy, so you are not a good fit", "if you're an iPhone game startup, you're not backend-heavy, so you are not a good fit", and yes, also "if you're a machine learning startup, you are not backend-heavy, so you are not a good fit".