in reply to Best/possible ways to dynamically use modules
Use RCS (or some other source control system) to protect yourself. If you don't want just anyone just walking in, commenting use stricts; and adding three globals, then control your source. You also get a log of who edited which source file when (and, if they're polite, what they did).
Another thought would be to go about getting all those "village idiots" to learn "The Right Way"(tm) to do things so as to not break your "Perfect Algorithms"(tm). Maybe they have a few ideas you didn't think of. Maybe one's a genius in disguise. Maybe not, but you'd never know it to look at them. :-)
More importantly, though, you start to get past the "Us vs Them" mentality that so many programmers have towards their users/colleagues/coworkers/village idiots. Maybe, just maybe, you can get one of them to evolve into a higher lifeform. Maybe a VB programmer. *grins*
------
We are the carpenters and bricklayers of the Information Age.
Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.
|
|---|