ra-mos

4 ms·

1.
by ra-mos 5y ago
“proposed solutions solve this” ~ every cryptocurrency/blockchain/web3 article ever written
2.
by ra-mos 5y ago
Your next metaphor is worse. If a steering system wan an invention/innovation than it deserves ip rights. What are you on? Should everything be equally competed in society, even after invention?
3.
by ra-mos 5y ago
Yes, because at one point in time that was an innovation. You said it yourself.
4.
by ra-mos 5y ago
You say that, but have you met my aunt? … /s (mostly)
5.
by ra-mos 5y ago
To be frank, you’re struggling with junior web dev problems. Learn to be an engineer.
6.
by ra-mos 5y ago
This and all the comments with similar experiences really just put a negative light on marriage.
7.
by ra-mos 5y ago
Could the issues be less presumptuous about googles business, and more technical? E.g the incorporation of NLP model(s) in search that don’t perform well in the wild? Curious about their query parsing as well. I can’t recall exact queries,
8.
by ra-mos 5y ago
Flatbuffers have been good in a demux/parallel architecture I’ve been managing. We split single requests into ~100-500 requests — each using the same Flatbuffer object (list of items). Each sub request reads header data to pull some pe
9.
by ra-mos 5y ago
Hoping your sentiment is sarcastic.
10.
by ra-mos 5y ago
Hey, 1. Our models act as building blocks for various feature apis/algos, but embeddings are required for all tasks. We have one major task which a user request sends their business items (think documents / docIds), anywhere from
11.
by ra-mos 5y ago
A lot of this is dependent on what “prod” means. If production applications, you are largely just retrofitting devops processes to incorporate model apis. Nothing really changes from how you deploy/monitor your systems. Now, production
12.
by ra-mos 5y ago
Novice question, when would you use something like this over something like lex/yacc? https://tldp.org/HOWTO/Lex-YACC-HOWTO-4.html