You wrote it in 10 minutes its under 50 lines and it performs the function you wanted it to do.
Your program is successful, so its users ask for enhancements
and new features, so you add another 50 lines, and another, and
another ... your little program grows to be so successful that it becomes
critical to your company ... and then you leave the company.
For small throw-away scripts, written by and for a single person,
your approach is fine. But it doesn't scale, especially for
production software maintained by teams.
Moreover, in my experience, small throw-away scripts, especially
successful ones, have a way of growing into thousands and
thousands of lines of critical functionality.
This sort of code tends to be fragile and difficult to maintain.
Yet the code "works", so getting approval to improve its design
and maintainability can be problematic.
After all, where is the ROI in rewriting a working system?
The cost of rewriting, the opportunity cost of not working on something else, changing the code risks breaking critical functionality
(especially likely without unit tests).
This topic is touched on in Unix shell versus 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.
|
