> -----Ursprüngliche Nachricht----- > Von: Andrew Timberlake-Newell > An: [EMAIL PROTECTED] > Betreff: RE: Perl Certifications ?? > > I've seen Perl used in "business environments" in each of the > following > roles: > > A) The primary development language > B) A co-primary along with PHP > C) One of many languages used on a per-task basis...with no real > primary > D) "Tool" usage for auxiliary support of another "primary" language > > The idea that Perl is merely an auxiliary/small-job language > is nothing > more than a misconception arising largely from the fact that it is > frequently used that way. (After all, despite the quipping of > TIMTOWTDI, we programmers are not immune from assuming that the first > way we've seen something done is the (only|correct) way to do it.)
Yes, Andrew, I think you are right: This may be the fact, because PERL makes it easy just to start and produce very fast some results. We are using PERL in two roles: A) The primary development language for a monitoring suite and B) "Tool" usage for auxiliary support of another "primary" language, namely Java. > Personally, I think that the Perl community could benefit from a > credible Cert.... Sorry, but I would like to contradict: My experience is, you should not search for the reason for bad programs in the language itself but in the knowledge of the programmers about software architecture. The programming language is only the tool for the fulfillment. The first step, which is independend from any language, is to think about what you will do. May be some of you are able to read german textes: they may have a look at: http://www.openquasar.de/ (the english part is not ready yet...) This site describes a standard software architecture for enterprise level software. Even if they describe it using Java, why don't we use PERL for that? You can screw this model down to smaller projects, which we do for some months for a refactoring of parts of our monitoring suite: With success :-) So my message is: Don't (only) certify a programmer for his language capability, but his capabilities of designing software. Or, in other words: Think about the roles of the programmers in your project: architects and / or workers, but even workers should have an idea of good architecture ;-) Dietmar > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:perl-win32- > > [EMAIL PROTECTED] On Behalf Of Bharucha, Nikhil > > Sent: Friday, February 06, 2004 1:10 PM > > > > PERL is kind of a jack-of-all trades language. It is a scripting > > language. In business environments (where certification means > > something) PERL is not the primary development language at the > > Enterprise level. It is an extremely versatile "Tool" to get small > and > > medium sized jobs done and done right. > > > > Certification? If you want to get certified get J2EE Certification. > > Know PERL to use PERL. PERL as a primary skill at the > business level > is > > not a good idea, but as an integral part of your skill set YES. > > > > At my place of employment we use PERL to get the misc jobs done (and > the > > crap still left around from the 90's internet boom -- still works > pretty > > good though!) > > _______________________________________________ > Perl-Win32-Users mailing list > [EMAIL PROTECTED] > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs > ____________________________________________________________ Hamburger Berater Team GmbH Dr. Dietmar Fiehn Telefon: 040/369779-0 Stadthausbrücke 3 (Fleethof) Telefax: 040/369779-99 20355 Hamburg eMail : [EMAIL PROTECTED] ____________________________________________________________ _______________________________________________ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
