2 ms·
I suspect this is a problem with any project once the original developers move on and there's a break in institutional knowledge about the architecture and desi
by kbenson 13y ago
I suspect this is a problem with any project once the original developers move on and there's a break in institutional knowledge about the architecture and design reasoning behind a project. I also suspect it's more of a problem the more powerful the ability of the language to introspect and self-modify. Lastly, I suspect this is also paired with gains in efficiency in the design and implementation phase.
If that's true, it's a matter of trade-offs, not a clear negative, and it becomes a matter of recognizing those downsides and dealing with them accordingly (whether that be avoiding certain features except where specifically called for, better documentation, or preventing that loss of institutional knowledge).
- spiralpolitik 13y agoAt least in the Enterprise world, the maintenance phase significantly outlasts the design and implementation phase in the majority of projects so any gains in those phases are usually dwarfed by the latter phases. The system I'm currently migrating has been in production for 10 years. The original developers are long gone, as are the generation after that. It's code archeology at its finest. As you say its a trade off, but IMHO its always better to pick maintainability over efficiencies in design and implementation for most long term projects. (Not you say can't write maintainable Perl, its just much more difficult than in other languages and requires a solid culture to support it).