> More experienced programmers know very well that the bug is generally in their code: occasionally in third-party libraries; very rarely in system libraries T

> More experienced programmers know very well that the bug is generally in their code: occasionally in third-party libraries; very rarely in system libraries This was the bane of my existence when I worked on testing Windows years ago. New SDETs almost invariably fell into the trap of assuming any automation error was a "test bug" instead of a bug in OS code, even if the OS code in question was written last week.