I don’t even see why them roughly representing time is a problem due to them raising in a fibonacci sequence.

If they were a day each, it’s not like the jump from 5 to 8 means it’s going to take 3 more days, but that it’s gotten more complex and maybe it’ll still be 5 or 6 days but I can’t be sure because this one has a lot more unknowns that might not reveal themselves until I’m into it. That’s why we’re forced to go from 5 to 8 and not a 6 or 7.

The uncertainty is built right into it, so it can’t be exact time, but at the same time trying to ignore that they’re still time related is stupid.

I can’t give this enough upvotes.

Oh man, there’s been a few times over my career where they asked me what seemed like an easy enough question to them, but it’s in some terrible legacy code that were never given any time to fix, that fixing itself would be a huge ordeal and I respond with something like, it’ll take a day or two to get a confident answer to that.

They usually say no thanks after that, but they have sent me down that rabbit hole before.

As a dev, this definitely triggered me a little.