...where applicable, code generators written in something more beautiful (Perl, anyone? :)) might be worth considering as a way to sweep the ugliness under the rug.
Damn straight. I did that once with an IVR control system called ... um ... well, I guess I've freed up those neurons (thank the gods). Anyhow, my task was originally set as "take this printed spec, and write a control script". By the time I left that job, the task had morphed into "run the XML file from which the printed spec was generated through this Perl script, then get the sysadmin to CVS the results onto the test swerver". Much pain was avoided.
The moral of this story seems to be: if you're doing something painful on the computer, you should probably write a program to do it for you. After all, that's what programs are for.
--
F
o
x
t
r
o
t
U
n
i
f
o
r
m
Found a typo in this node? /msg me
% man 3 strfry
-
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.
|
