It's interesting that we think of code as this human-to-machine language.
Sometimes we remind ourselves that yes, somebody is going to have to read this in a while.
Think of that. What you write is... text, like a book!
What people do in book publishing is relevant to programming. We should have editors too, somebody to go through our code and say "nah, this needs work."
I've always been of the mind that programming is inherently a two-man job. This is perhaps the reason.
“Programs must be written for people to read, and only incidentally for machines to execute.” —Abelson & Sussman, SICP, preface to the first edition
This is why code reviews are strongly correlated with higher-quality code, and why pair programming is a good investment.
Erm, that's called code review. We do it all the time.