Why is Git Autocorrect too fast for Formula One drivers?
blog.gitbutler.com
Why is Git Autocorrect too fast for Formula One drivers?
1–10 of 248 posts
Re: Why is Git Autocorrect too fast for Formula One drivers?
#2Deciseconds?? There's your problem. Always work in seconds when forcing a function for your users.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#3Deciseconds?? There's your problem. Always work in seconds when forcing a function for your users.
Maybe he meant dekaseconds? Still weird though..
Re: Why is Git Autocorrect too fast for Formula One drivers?
#4I'd be interested to know if any F1 drivers actually use git.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#5Deciseconds?? There's your problem. Always work in seconds when forcing a function for your users.
Seconds or milliseconds (e.g. if the setting must be integer) would've been fine as they are widely used. Deciseconds, centiseconds - wtf?
Re: Why is Git Autocorrect too fast for Formula One drivers?
#6I'd be interested to know if any F1 drivers actually use git.
[deleted]
Re: Why is Git Autocorrect too fast for Formula One drivers?
#7I'd be interested to know if any F1 drivers actually use git.
Not sure, but I do personally know two high profile Ruby developers who regularly race in the LMP2 (Le Mans Prototype 2) class - DHH and my fellow GitHub cofounder PJ Hyett, who is now a professional driver, owning and racing for AO (https://aoracing.com/).
I mostly say this because I find it somewhat fun that they have raced _each other_ at Le Mans last year, but also because I've personally seen both of them type Git commands, so I know it's true.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#8I sometimes have this realization as I'm pressing enter and reflexively press ctrl+c. As someone whose typing speeds range from 100 to 160 WPM, this makes sense. Pressing keys is much different from Formula One pit stops.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#9Deciseconds?? There's your problem. Always work in seconds when forcing a function for your users.
Maybe he meant dekaseconds? Still weird though..
It reads like the intention was that turning the parameter (0/1) command into an integer parameter, where the previous value enabled = 1 should behave reasonably close to the old behaviour. 1 deciseconds is arguably close enough to instant. If the parameter were measured in seconds, the command would always have to wait a whole second before executing, with no room for smaller delays.
Re: Why is Git Autocorrect too fast for Formula One drivers?
#10Deciseconds?? There's your problem. Always work in seconds when forcing a function for your users.
Maybe he meant dekaseconds? Still weird though..
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.