2 ms·
But isn't it almost always written by someone else? Except in very specific instances is there ever an application whose full life is touched only by a single d
by joekrill 12y ago
But isn't it almost always written by someone else? Except in very specific instances is there ever an application whose full life is touched only by a single developer. People change jobs, move on to other projects, etc.
- wpietri 12y agoI don't think that's true in a well-meshed team environment. If there's substantial continuity of team members, there's a house style and a shared set of approaches that make the code "our code", even if you're looking at parts that happened to be written by people who had left. It's especially the case in pair programming shops, where there's a lot more opportunity for transmission of the history and intent that went into the code.
- watwut 12y agoThat holds true only if the code is repetitive, for example big site with a lot of similar pages. If the code is not repetitive, e.g. composed of modules that do very different things or implement non-trivial algorithms, then knowledge of one part does not necessary translate into another. And if it it is big enough, then everyone knows only small subset of it all, whether you pair program or not.