Lemmy learns exponential math.
Mostly joking, thanks for doing the math.
Comment on Programmer tries to explain binary search to the police
Pazuzu@midwest.social 11 months ago
I thought this had to be hyperbole, so I did the math myself. I’m assuming human history is 200,000 years as google says, and we want to narrow this down to the second the bike disappeared. also that the bike instantly vanished so there’s no partially existing bike.
each operation divides the time left in half, so to get from 200k years (6.311×10^12 seconds) to 1 would take ~42.58 divisions, call it 43. even if we take a minute on average to seek and decide whether the bike is there or not it would still be less than an hour of manual sorting
hell, at 60fps it would only take another 6 divisions to narrow it down to a single frame, still under an hour
Lemmy learns exponential math.
Mostly joking, thanks for doing the math.
History is about 10k years, the 200k years is mostly pre-history. People didn’t write stuff down until they invented agriculture and needed to track trade between owners, workers, etc
True and interesting to note, OOP says ‘dawn of humanity’ though, not recorded history, so taking that as ‘human history’ is valid.
Yeah, I’m used to the narrower meaning of “history”, meaning recorded. I like that definition as it lets you differentiate between it and prehistory.
Definitely a useful distinction.
Well, in this case it must have been recorded on video, so could as well start recording before inventing the writing
Combine AI pattern recognition and quantum computing, and this search could be completed before it was even started.
We can go deeper!
Just watch at 3X!
A minute to decide if there is a bike in the picture really ?
As a robot, finding bikes in pictures is really hard, okay
Takes time to precisely seek to each timestamp, but really I just meant that an hour was reasonable even with a lazy cop doing the search
They must be really bad at solving CAPTCHA
Ever heard of a logarithm? If you haven’t, you just reinvented it.
Also, your math is wrong: log base 2 of 200,000 is ~18
You did 200k years. You need to do seconds. Their math is right.
rckclmbr@lemm.ee 11 months ago
I regularly bisect commits in the range of 200k (on the low end) for finding causes of bugs. It takes me minutes. Pretty crazy