kfrane

When I see that, my first thought is that there are a bunch of features missing from the original.

That's a beautiful writing style. Feels like there's some Anthony Bourdain in it :)

From my experience with billing systems it is usually not possible to refund a transaction after 6 or 12 months.

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.

It's a bootstrapped business, no investors/board.

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.

One more that I've heard just recently: "If your code is just juggling with pointers/references, it is likely that it isn't doing much useful. It is only when it starts dealing with actual values that it is starting to do something useful."

Hooks are a step in the right direction, I just have a feeling that having to wrap in useCallback and useMemo and having to add dependencies manually can't be the final step of web app development. I look into the author's suggestions for the next generation of hook api in other libraries. However, I still don't want to rely on those libraries in large long living projects.

Nobody will, at least if there's any truth in this article

I'm not sure, it might be. If you're not careful, CPU can become bottleneck when you have a 10Gbit network card.