> It's asking somebody who writes code to now read and debug others code. Writing code has always involved reading and debugging your own code, at an absolute

> It's asking somebody who writes code to now read and debug others code. Writing code has always involved reading and debugging your own code, at an absolute minimum, even if you did everything solo. In any remotely serious collaborative effort, it also involved code review and collaborative debugging; people use issue trackers and assign themselves and each other "tickets", which often involve fixing issues that are ultimately caused by someone else's code. > It can actually be harder to find the the bug in a tricky piece of code than it can be to write your own correct code from scratch. Part of the point is to reject tricky code exactly because it is tricky (as this is rarely actually necessary).