A really common time-wasting debugging scenario follows this pattern:
- programmer is working with a new technology or new technique that is somewhat mysterious to them
- something (something simple) goes wrong that has nothing to do with the new tech
- programmer assumes the error is in the “mysterious” code part and spends many hours on a wild goose chase
Is there a term for this? It seems to me it deserves a name of its own, if there isn’t one already.