Sure, one little hobby horse, e.g. "inversion of control" can run amok to negative effect (looking at you, Java projects with object traces 75 layers deep) but

Sure, one little hobby horse, e.g. "inversion of control" can run amok to negative effect (looking at you, Java projects with object traces 75 layers deep) but that doesn't make idempotency or inversion of control into bad ideas. A bit of pragmatism goes a long way, like Python's odd x = (some_tuple,) . . .syntax amidst its generally clean approach. Inflexibility itself is the bugaboo.