I would prefer 3.5mm over Bluetooth, but keep in mind most people get their music off their phones and (almost?) no modern phones have headphone jacks. Dongles are a thing, but meh.
Additionally, modern Bluetooth devices have very little friction in my experience.
If you can get the exact same result for less cost (time and money), why not? Things like enjoyment don't factor in since they can't be directly converted into money.
Netflix is paying for the infrastructure because for every byte that Netflix "pushes" there is a "pull" side who is paying for their residential internet access. What is the consumer paying the ISP for if the ISP is charging every service that the consumer is using more money separately?
That's assuming that hiring a person is the exact inverse of firing someone, which is often not the case. Firing someone has more negative effect than hiring's positive effect when e.g people move, leave previous jobs (possibly), have children, buy houses.
I assume they are talking about E2E-encryption, since that would prevent them from spying on their users even if they wanted to (assuming the client doesn't leak the key).
That said, E2E-encryption doesn't come without drawbacks, for example you would lose all your messages if you lost access to your device and any backup mechanism.
Unless I did something wrong with my setup the elixir LS is kind of lackluster compared to a full IDE. It doesn't have any automatic refactoring (even variable renaming) nor does it provide automatic detection of syntax errors. It's pretty much just symbol lookup and some autocomplete functionality.
This is what I assumed considering it had the right answer but the explanations were garbled. Presumably it reproduced the answer, and then some weird patchwork of the various explanations in its training set.
I don't get region restricted apps. Sometimes it might make sense, but 99% of the time it's just unnecessary and achieves nothing except annoy travelers. Is there some incentive for app developers to region restrict their apps?
Yeah, I find the signature example kind of unimpressive because it can just pick up the meaning of the code from the function name and variables, which an experienced human can do just as easily. If it could get "validates a signature with secret key" when all the variable names are obfuscated it might be useful in some code bases.
Some make direct sense like the tree/forest, others you have to deep dive into their history for them to make sense (if at all).
For example, the character for people (民) comes from the image of a person being pierced through the eye, which was done to mark slaves in ancient China. Eventually the character and meaning evolved to the way it's used now.
Indeed. I read the book in hopes of getting a good intro to TDD after only picking it up by osmosis (which, as proven by the discussions here, is not a good way to learn TDD) and it definitely goes against the maximalist interpretation as described in TFA. While there are examples showing the minimal code-approach he is very explicit about the fact that you don't have to write your code that way.
One thing I liked specifically was his emphasis on the idea that you can use TDD to adjust the size of your steps to match the complexity of the code. Very complex? Small steps with many tests, maybe using the minimal code-approach to get things going. Simple/trivial? A single test and the solution immediately with no awkward step in between.
If your goal is to avoid coupling tests to implementation then TDD seems like the most obvious strategy. You write the test before the implementation, so it is much harder to end up with the coupling than other strategies.
In some cases there might be local laws involved. If you buy a Samsung (or LG, but they don't make phones anymore) in Korea it will come with call recording available.
As someone with an inbox-zero obsession, I don't pretend to have any logical justification for it, I just really don't like seeing those unread markers. Same for any app that shows any kind of "look here" marker.
For my personal email, inbox-zero generally means actually reading most emails I get, because I aggressively unsubscribe/mark spam/auto-delete emails I don't want to get. My work email gets a lot more emails I don't need to look at, so there is a lot of automatic filtering and "mark all as read".
My main practical use-case is that I will leave emails unread intentionally if I can't deal with them at the moment. If I had thousands (or even dozens) of unread emails I'd have to track those separately.
Additionally, modern Bluetooth devices have very little friction in my experience.