It sounds like his experience is drawn mainly from being a one-man team working on his one-man projects.
Even in real hard engineering fields we see teams responsible for specific subsystems and components, which they need to test and validate.
By "unit tests" Knuth is speaking of tests that each test just one part of the program in isolation, mocking out the rest, and also more broadly about the practice of "test-driven development" which has this as its prerequisite. He means he finds it simpler to just write the whole program up front, and test it wholesale.