One of my idiosyncracies as a developer is that I use (rounded) powers of e anywhere I need to tune some constant (e.g. timeouts). For example, where most people would specify a timeout of 60 seconds I would specify a timeout of 55 seconds (i.e. round(e⁴))
The reason I do that is that I find that powers of e make more natural snapping points for constants that helps cure my decision paralysis. Powers of e are both (A) coarse-grained enough that there aren't too many to pick between and (B) fine-grained enough that one of them will be suitable for the task at hand. I'll just go up and down powers and be like "hmmm, 20 seconds seems too low, 55 seconds is … okay, 148 seconds is … too high, 55 seconds it is"
The main downside of this approach is that I have to explain this every time my code is reviewed when coworkers are like "Hmmm. 55 seconds is an oddly specific number. How'd you pick that?" and then I'm like "Actually, it's a very natural number to select"
