Part of this is the problem of "best practices" which should more rightly be called "usually best practices". Sometimes you're better off using a goto statemen

Part of this is the problem of "best practices" which should more rightly be called "usually best practices". Sometimes you're better off using a goto statement, or hard-coding a constant; but it's hard to justify unconventional choices to any team. It's particularly hard for programmers and engineers to know when to buck convention, because the combination of breadth and depth of domain knowledge makes it really hard to ever attain "expert" level in both.