> any serious legal situation (like a contract) is going to want a human in the loop to verify that the translation is actually correct
I hope you're right, but when I think about all those lawyers caught submitting unproofread LLM output to a judge... I'm not sure humankind is wise enough to avoid the slopification.
I still can't figure out how pg_trgm is supposed to work for multi-term searches and how to ensure the dictionary table it needs stays up-to-date. Is there a good writeup somewhere?
Because remote work was the only work in 2020 and 2021, yet a large majority of businesses continued to function mostly well. Some even exceeded their average results.
I know, right? I thought COVID proved definitively that remote work is not just possible but equal to in-office work. I really want to understand the counterarguments, but all I see is oblique assertions like "true creativity requires body language." I'm keeping an open mind, and I acknowledge that in-person chat features much higher comm bandwidth than video chat, but I'd like to see a well-reasoned explanation of what exactly a business loses by allowing its employees the freedom to manage their time and workstation setup.
> My guess is their voice, sms etc all are IP these days which was impacted by their BGP issues.
Impacted, yes. But "no service"? That's dubious.
I hear you on foreign SIM working. I got online at a cafe just long enough to buy a Yessim eSIM. When I activated it and turned on data roaming, I had LTE working on... the Rogers network! That I didn't expect.
How does that relate to the Rogers cell service outage, though? Surely SMS doesn't require BGP?
It feels like there's a big, fundamental problem affecting a variety of Rogers infra, where BGP and cell problems are just symptoms we can observe. CloudFlare says it looks more like a failure than an attack; I'm not entirely convinced.
I'd find it more convincing if you've been living in, say, Lisbon and charging Seattle prices. If I were hiring devs in Seattle, I'd be delighted to pay them EU wages.
> you should be prepared for your results to be never-consistent
Isn't this a core feature of distributed systems? How can you be "consistent" if there's a network failure between some writer and the stream? How can you tell a network failure from a network delay? How can you tell a network delay from any other delay?
And finally, how can you even talk about "up-to-date" data if the reader doesn't provide their "date" (ie, a logical timestamp)?
I hope you're right, but when I think about all those lawyers caught submitting unproofread LLM output to a judge... I'm not sure humankind is wise enough to avoid the slopification.