I first saw this joke back in the days of 8-bit home microcomputers. Of course then it only needed 256 lines of code, and took up about 8k of your precious, precious RAM.
There’s some truth to it. I’ve seen devs not clarify something from the designs with other stakeholders due to lack of social skills. You end up with something they implemented to the spec, but makes no sense it reality.
I do not get why it would work in that case. I assume the scenario is someone with a bike coming, doing theft, then leaving with the same bike.
Therefore there will be a period without bike, then a period with bike, then a period without bike again.
Let’s assume there is no bike on the particular moment viewed. How do you know whether it occured before or after the theft? If you make the wrong decision, you get stuck on an endless binary search… Unless you take note at each timestamp where you made the decision, draw a tree of timestamps, and go back the tree if your search is fruitless but that’s much more complicated than what this post says.
You’re making this way more complicated than it actually is. The guy definitely can give estimates for when he parked the bike and when he found out that it was stolen. It’s not that complicated.
Basic rule if someone claims X magically solves a problem they don't follow X and are a huge generator of the problem.
For example people who claim they don't need to write comments because they write self documenting code are the people that use variable names x1,x2,y, etc..
Similarly anyone you meet claiming Test Driven Development means they have better tests will write code with appalling code coverage and epically bad tests.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.