Think about Loose Coupling | |
PerlMonks |
Re: Re: Re: When to use perlby cciulla (Friar) |
on May 31, 2003 at 14:45 UTC ( [id://262072]=note: print w/replies, xml ) | Need Help?? |
Although I wouldn't catagorize "right tool for the job" as "politically correct", you do bring up a valid point. With a caveat.
Pick the one you find most pretty and are most familiar with. I concur that when the developer has the latitude to choose how the work is done, then pick the tool that you are most comfortable with. Unless you are your own customer, this doesn't occur often as your customer will have (for good or evil) a standard development platform. Apparently, the OP's boss found that rare customer, and chose perl. The OP has a choice: use perl, beat feet, or suggest that another tool may be in order. Needless to say, the last two are very closely related. On my current assignment, my customer chose WebLogic, Java, and SQL Server. While I am within my rights to use perl to automate some of the more tedious aspects of development, I would be entirely out of line to put any of this into production. If I felt strongly about implementing a solution in some other tool, it is my responsibility to recommend this to my customer. It is equally my responsibility to abide by their decision, or move on.
COBOL has no advantages. COBOL needs no advantages. I disagree. While my personal preference is never to look at COBOL again, if my job depends on me dusting off my Stern & Stern, guess what I'll be doing. Bottom line: "Him that pays, says." Cē
In Section
Meditations
|
|