3 ms·
As a result code maintenance can become a huge headache due to someone not understanding the idioms used by the person who originally wrote the code. I don't u
by chromatic 13y ago
As a result code maintenance can become a huge headache due to someone not understanding the idioms used by the person who originally wrote the code.
I don't understand this. If this hurts you, wouldn't you have the same problem with domain knowledge, except an order of magnitude worse? Why are your developers not talking to each other?
- Patrick_Devine 13y agoTeams are dynamic, not static. You can have new hires, you can lose people and you can get code written by others that you have to maintain (especially the case with CPAN). I agree this is also a problem with domain knowledge. The second you commit something to your code base the clock starts ticking. The further away from your own code, the harder it is to have context and the more difficult it is to fix problems. If you feel like you can jump back in to your Perl code easily after a prolonged absence, by all means, do it. My point was only that in Perl, it's easy to use many different idioms which not all coders are familiar with. This can make debugging more difficult.