> someone who has settled into a set of "correct" answers and now sees other people not adopting their personal outlook on code as a failure to learn. Real exa

> someone who has settled into a set of "correct" answers and now sees other people not adopting their personal outlook on code as a failure to learn. Real example #1: I warn John Doe that his new endpoint will crash in a specific scenario. John Doe dismisses the warning since "it's not likely to happen in the wild". QA call it out soon after it's uploaded to our test environment. The error has a chain effect where it prevents them from testing other stuff. Real example #2: I warn John Doe that we just committed a flaky test to the develop branch, and I submit a PR to fix it. John Doe closes the PR since "for now we must accept tests fail in mysterious ways". Soon after, Doe Johnson who works in another team is blocked by said test. He spends an hour or two coming up with the same solution I did. In both cases we burnt money needlessly, because John Doe is too stubborn to accept our team's code is not perfect.