Reading this post, the term "software archeology" and "programmer archeologist" come to mind. (Thank you, Vernor Vinge, for the latter concept.)
I like to say that the danger of software archaeology is the inevitable discovery of coprolites...
Why is Git Autocorrect too fast for Formula One drivers?
31–40 of 248 posts
Re: Why is Git Autocorrect too fast for Formula One drivers?
#32Earlier quoted context omitted.
We had this debate internally at GitButler. Deci versus deca (and now deka, which appears to also be a legit spelling). My assumption was that 1 full second may have felt too long, but who really knows.
deci is 1/10, deca is 10/1. So decisecond is correct.
I understand, I meant I tried to say the word “decisecond” out loud and we debated if that was a real word or if I was attempting to say “deca” which was understandable.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#33IMHO this is a great example of "creeping featurism". At best it introduces unnecessary complexity, and at worst those reliant on it will be encouraged to pay less attention to what they're doing.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#34According to Formula 1 web site drivers start on average after 0.2 seconds since the red lights go out https://www.formula1.com/en/latest/article/rapid-decisions-d...
Anyway, 0.1 seconds would be far too short even for them, which have a job based on fast reaction times.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#35I think it makes sense, if I typed something wrong, I often feel it before I can read it, but if I already pushed enter, being able to ctrl+c within 100 ms is enough to save me. I'm pretty sure I've also aborted git pushes before they touched anything before I put this on, but this makes it more reliable.
Maybe worth noting here that 100ms is well under the human reaction time. For context, professional sprinters have been measured to have a reaction time in the ballpark of 160ms, for pretty much everyone else it's higher. And this is only for the reaction, you still need to move your hand, press the keys, etc.
In this case the reaction starts before you hit enter, as you're typing the command
So, you type `git pshu` and realise you made a typo before you've finished typing. You can't react fast enough to stop hitting enter but you can absolutely ctrl+c before 100 more ms are up
Re: Why is Git Autocorrect too fast for Formula One drivers?
#36I think it makes sense, if I typed something wrong, I often feel it before I can read it, but if I already pushed enter, being able to ctrl+c within 100 ms is enough to save me. I'm pretty sure I've also aborted git pushes before they touched anything before I put this on, but this makes it more reliable.
100 ms is an insanely short window. I would say usually even 1000ms would be too short for me to recognize and kill the command, even if I realized immediately that I had done something wrong.
It's much too short to read an output, interpret it and realize you have to interrupt
But often you type something, realize it's wrong while you are typing but not fast enough to stop your hand from pressing [Enter]
That is one of the only situation 100ms would be enough to safe you
That being said, the reason in the article for 100ms is just confused commander. Why would anyone:
1) encode a Boolean value as 0/1 in a human readable configuration 2) encode a duration as a numeric value without unit in a human readable configuration
Both are just lazy
Re: Why is Git Autocorrect too fast for Formula One drivers?
#37Deciseconds is such an oddball choice of units. Better to specify the delay in either milliseconds or seconds - either are far more commonly used in computing.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#38Earlier quoted context omitted.
100 ms is an insanely short window. I would say usually even 1000ms would be too short for me to recognize and kill the command, even if I realized immediately that I had done something wrong.
It's much too short to read an output, interpret it and realize you have to interrupt But often you type something, realize it's wrong while you are typing but not fast enough to stop your hand from pressing [Enter] That is one of the only situation 100ms would be enough to safe you That being said, the reason in the article for 100ms is just confused commander. Why would anyone: 1) encode a Boolean value as 0/1 in a…
> "Why would anyone ... encode a Boolean value as 0/1 in a human readable configuration"
It may be lazy, but it's very common!
Re: Why is Git Autocorrect too fast for Formula One drivers?
#39Reaction times differ by types of stimulus, auditory is slightly faster than visual and tactile slightly faster than that at 90 - 180 ms
So if git gave you a slap instead of an error message you might just about have time to react.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#40Deciseconds?? There's your problem. Always work in seconds when forcing a function for your users.
This may be something specific to Japan, which is where the maintainer is from. In the Japanese industrial control systems that I’ve encountered time is typically measured in this unit (100 ms).