Code Review
Rachel Laycock, CTO at Thoughtworks, lays out a strong argument against code review as the final boss in the software development lifecycle. Laycock suggests pair programming and team whiteboard sessions as techniques to separate the efforts that require human judgment from the toil of linting, formatting, fixing bugs, and the other detritus of the review process. I'm inclined to agree with her. Although I wonder, if we no longer review all this code, then what will we review? I don't know how you codify the wisdom gained from looking over your peer's shoulder, or if a picture of a diagram drawn in dry-erase marker could serve as a durable artifact: