even possible with a some of them, but even in that case they're usually not "refunding" as much as they're just "making a new transaction for the same anount the other way" which does the same at the surface until reversals, voids or rejections happen and it all becomes a mess.
Typing speed might not seem that important if you're looking at the speed of typing and the overall amount of code that an engineer produces that ends up in a PR. But it might take 10x more code that are ephemeral versions that lead up to the full solution. If you're very comfortable with typing and editor commands to manipulate code efficiently then you can iterate faster, creating more intermediate versions of the code that then lead to better overall solutions just because you've tried out more stuff.
If I understand that correctly, it would mean that running a function like this on two threads f(1) and f(2) would produce a list of 1 and 2 without interleaving.
def f(x):
for _ in range(N):
l.append(x)
I've tried it out and they start interleaving when N is set to 1000000.
I migrated from gmail to proton then to fastmail and I can now really appreciate how much more polished gmail was.
My biggest pain is fastmail's ios app, e.g. clicking on an email notification will in 50% of cases result in fastmail's app to open in an unresponsive state where I have to forcefully quit the app and start again. It's been like that for close to two years now.
I think most business people dont care about clients at all because they use IMAP/SMTP/carddav/caldav.
Once you have more than one mailbox then its kinda the only way. So apple mail, thunderbird etc. And then you mostly get some quality provider mailbox.org, fastmail, infomaniak or whatever but its all the same.
I was a bit confused when looking at the English example for Chain-Of-Thought.
It seems that the prompt is a bit messed up because the whole statement is
bolded but it seems that only "appetite regulation is a field of
staggering complexity" part should be bolded. Also that's how it shows up in
the o1-preview response when you open the Chain of thought section.
Thank you!
I almost gave up because there was a lot of formatting issues when sending epub3 or kindle versions to my Kindle using Calibre. What saved me was using epub3 format and sending it through Send-To-Kindle. Now it looks terrific.
That's why I always write a BEGIN statement before executing updates and deletes. If they are not instant or don't return the expected number of modified rows I can just rollback the transaction.