On Thu, Mar 06, 2003 at 10:25:57AM -0800, Paul wrote: > I'm sold -- I write most code as object modules now. > > My coworkers aren't interested in dealing > with the learning curve for objects, and don't care to hear about it.
I think you have bigger problems than teaching your coworkers about objects. Sounds like they wouldn't take well to using a functional style either, or learning about logic programming. What about test driven development, or XP? Whilst different paradigms and methodologies suit different problems, you can only use them if you know about them. I cannot understand a professional in any field, and particularly one as young as ours, who wouldn't want to keep learning and improving. Doubly so if they can do it on company time. > Obviously, though I understand it well enough to use it, I can't > explain the advantages. They say "you could just do that with > so-and-so", and I can't communicate the amount of work saved by the > abstraction. Since (virtually) all computer languages are turing complete, maybe you should suggest all future development be done using vi macros. Presumably you are using Perl for the productivity benefits it brings. Used appropriately, OO can provide further benefits. You're also cutting yourself off from a large part of CPAN if you don't want to deal with objects. Having said that, OO has been heavily hyped, and there is bound to be a backlash against that. It is not a panacea, but it is very effective in its place. -- Paul Johnson - [EMAIL PROTECTED] http://www.pjcj.net -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
