Toxic Experts

After writing an introductory explanation of Big-O notation, Ned Batchelder received a comment from a reader who scolded him for omitting a technical detail of algorithm analysis. Batchelder argues that the detail was interesting but unnecessary for his intended audience: working developers seeking a broad, practical introduction, not an exhaustive treatment. He uses the exchange to describe “toxic experts” - people who turn specialized knowledge into a boundary between insiders and beginners, choosing condescension over teaching. Such experts often treat a particular skill, such as assembly language, pointers, or a formal analysis technique, as a test of who deserves respect. These topics can be valuable without being prerequisites for doing good work.

Batchelder says expertise also requires understanding what learners need and when technical details matter. Knowledge without empathy and the ability to connect is of limited use, and beginners should not mistake a hostile expert’s judgment for a verdict on their potential. Responses to his argument add important qualifications: some commenters recommend separating useful factual criticism from insulting delivery, while others stress that accuracy matters and that omitting fundamentals can have consequences in critical software. A commenter also argues that experts may become arrogant after years of being dismissed. The exchange ultimately frames the challenge as balancing correctness with accessibility: technical precision serves understanding, but it should not become a weapon for excluding people.