It might be an idea to introduce your management to the concept of metrics. In the mean time, put in place the means of gathering the information required for the metrics.
This is a good way of turning a technical problem (having a programming language imposed on you) into business language that pointy haired bosses understand.
What I am talking about:
- Size of application: How many lines of code? How many pages of documentation? Estimated effort required for Java rewrite in man-days.
- Maintainability: How stable will the application be in Java? in Perl? If it ain't broken don't fix it. What is the Mean Time to Fix problems (mttf)? What is the cost of maintenance in terms of head count?
- Flexibility: How easy is it to add new functionality, and meet changing business requirements? How often do business requirements change? How much development-lag is there in each business driven enhancement?
You may find that this approach will help with whatever programming language you are using. It may help you get hard evidence that the company should stick with perl.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|