Re^3: Modules, Frameworks, and Reinventing the Wheel

[Velaki]

I agree. Asking people you trust is good; however, I've noticed that the people the new ones trust -- where I work -- go by the concensus of the local perl experts chatroom, which is never of one accord, since many of the "experts" in there are just as green as the ones asking the questions. Hence, all the module overuse, and no one appears to have learned the whys and wherefores of perl enough to give reasoned opinions. They simply chant, "Module::Module::Module."

As I've said before, I'm all for modules. They're good for what ails ya, but it's like going to the doctor and upon being asked, "Where does it hurt?" replying, "You're the doctor. You tell me."

I would rather see the new programmers understand perl, and know why they're using the modules, and how the modules help them, rather than bolting together a disjoint set of modules, and gluing them together with really nasty code.

Maybe I should start some basic perl lectures to help the new programmers learn how to use modules more effectively, by showing them how their implementation and glue code may be written.

-v