This reminds me of this old Feynman video where he talks about how people use different methods in their heads when counting, seems relevant: https://youtu.be/Cj4y0EUlU-Y?t=135
Interesting, for me it happens sometimes if I'm badly hungover. Instantly after closing my eyes, I start seeing cartoon-like shapes that rapidly mutate to something different. Usually it's faces of people. The shapes are very dim, and black and white. But I really do "see" them as they were there.
Now I want to attempt using the technique in TFA to improve this "skill", also interested in using this for falling asleep faster and maybe even to successfully using the WILD technique for lucid dreaming, which I was never able to do.
I think they mean peloton. It's not English, I believe it is French, meaning a group of bicyclers. In this context it refers to the peloton leading the race.+-
>I hate that UI. Why can't we just click on the "man", and then click on a spot to drop it?
You can, actually. When you click it, all of the roads that have street view are highlighted with blue color. In this mode you can just click on the roads to go to street view.
I saw once a support person from $COMPANY_I_WORK_IN ask a client to send their private key in email, so they could troubleshoot something. I pressed "Reply all" and called it out, and was yelled at later.
I wonder what model this site is using. FWIW I tried with ChatGPT (both GPT-3.5 and GPT-4 versions), and it does a better job (tried multiple times). On one attempt it even said the Floor name is misleading:
The given code is a C-style implementation of the "fast inverse square root" algorithm. This algorithm computes an approximation of the inverse square root of a given number (1/sqrt(x)). The code does not actually compute the floor of a floating-point number, so the function name "Floor" is misleading.
Text is broken into something called "tokens" [0] for GPT. It doesn't work on individual characters. That explains why it always fails these character counting questions.
I completely disagree. When I see embedded Google Map I always try to zoom it by scrolling, but then get frustrated when it scrolls the page instead and I'm supposed to press control for zooming.
I'm sorry if I sound rude. I don't mean to be. I'm just saying that backing up your git workspace to recover from rebases or merges gone wrong is not necessary. Those are not "surgical tools", they don't modify existing commits. (edit: yes you can "edit commits", but they only create new commits, the old commits are not deleted in the process and they can still be found easily)
When you commit in git, that saves the whole project as a "snapshot". If you find yourself lost in some rebase hell or whatever, just reset HEAD back to a previous commit. It's simple as that! (git reset --hard <commit>)
Why I decided to reply to your comment was because this is a very crucial part of learning git. When you realize that you can always go back to what was before, you can start experimenting more freely.
This is so wrong. :) With git you exactly do not have to backup your local workspace, because it already is backed up in git.
If it is committed, it is safe. You can go back to it. If you messed up your branch, just reset it to something that was good. No need to do manual backups.
AFAIK apple varieties don't change over time, because the same genes are used over and over by grafting the trees instead of growing from seed. This is because seedlings produce wildly different characteristics from their parents.
One important aspect of logging is to include enough information when something fails. This sounds like it should be common sense, but I have seen this too many times:
Why not include at least the hostname and port? And what connection is this exactly that failed? You might be able to find out what it was trying to connect to based on the stack trace, but that requires knowledge of the internal structure of the software.
This seems to be a common problem in software written in Java, I don't know why exactly. Maybe something to do with the way exceptions are handled, so that the relevant information is not available when printing the error?
I hate the praise that fail2ban gets. It is useful, but it is not securing anything really, unless maybe you run a public ssh box that has other users who have bad passwords. It will keep the logs cleaner though. A better way to secure SSH on a web server would be to restrict access by firewall and/or disallow password logins.