antipattern i've noticed in large codebase in a language with default values for keyword arguments:
people put defaults in for named arguments deep inside the call stack, even when the parameter is "always" passed.
now there are multiple defaults, at multiple levels, and its unclear to the casual reader which default is true.
and when forgetting to pass in the parameter that "should" always be passed, you don't get any error from your programming language.