The title should have been "A lot of unit tests does not mean you've written good code." I think the implications of the post are correct, but I think it would

The title should have been "A lot of unit tests does not mean you've written good code." I think the implications of the post are correct, but I think it would be incorrect to say that if you have a lot of unit tests it means poor code. There are engineers who have a difficult time seeing things architecturally (for reasons ranging from ability to priorities). Razor sharp focus can produce a lot of unit tests while missing some refactoring that might have helped reduce the code base, and therefore the number of unit tests. [Edited]