You could apply strong dictatorship on the perl files and say that they must pass a parser that checks the code for the proper things. A standards parser then it might
work!
This is exactly one of the things I was trying to get at with my last node.
I would like to check a huge pile of code, spread across multiple dirs,
users, etc... and format them all corectly, document them in pod, convert the pod into an html api listing,
check for inconsistancies in the api ( check code calls to functions against
the included module's qw ( api_function1 ) statements and finally, check the code into cvs.
It seems like that's quite a tall order.
We are also trying to scale perl up to a size that it probably doesn't naturally
fit into. TMTOWTDI probably means that the way you decide to do it
may be completely foreign to your fellow developers, any kind of standards checker/parser,
or even yourself in a few months ;-) However, a small team of people fluent in conversational Perl
will be able to write the code that a company needs faster than a fleet of "baby talkers".
Trouble is that in this job market, all most companies can seem to hire/retain are the less fluent,
translation dictionary toting, "just visiting for the money" computer science tourists. It's
reassuring to hear that other people are in the same situation,
but I don't hear that many success stories. That's quite discouraging.
I hope this post doesn't come off as a rant because I don't mean for it to be so... I would like to see
problems like these affect a change in Perl rather than result in a lot of complaining and hot air. We are going to try to make it happen in our company... If we can't we'll be forced to move some code to other, stricter, languages
-pos
The truth is more important than the facts.
-Frank Lloyd Wright | [reply] |
I applied for a company that worked with a huge perl based website. They had developed a good standard to handle the scripts by running them through a "wizard" that put in the right constructs for the "shop standard". They had about 5 person working on the code
Now you're might be asking for what does this apply to your problem:
Trouble is that in this job market, all most companies can seem to hire/retain are the less fluent, translation dictionary toting, "just visiting for the money" computer science tourists. It's reassuring to hear that other people are in the same situation, but I don't hear that many success stories. That's quite discouraging.
They wouldn't hire me. The reason they gave me was that I was not quite right on their specification.
So they actually looked carefully on the testcode that I did on the interview and said to themselves: "This guy isn't going to follow our specification"!
So their are companies that actually try to avoid the "tourists" and people that aren't as adaptable to the standard that they apply!
/JanneVee
| [reply] |
