4 ms·
> The easiest time to catch mistakes is early. pair programming and the articles proposing it do nothing to help catch mistakes early. i would argue that they
by nikofeyn 7y ago
> The easiest time to catch mistakes is early.
pair programming and the articles proposing it do nothing to help catch mistakes early. i would argue that they even delay catching mistakes due to what i'd call deconstructive interference during the implementation process.
there are plenty of much more systematic ways to catch mistakes earlier than just slapping pair programming onto the software process.
- jacques_chester 7y agoMy experience is that it does catch mistakes early. And it's not mutually exclusive of other ways of spotting errors, it's reinforcing.
- nikofeyn 7y agowith pair programming, you have two people supposedly in the same head space, if it's working as sold, writing code. the benefit of tests and code reviews is that they come from a different head space than what the code was written in.