Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

petdance (2468)

petdance
  andy@petdance.com
http://www.perlbuzz.com/
AOL IM: petdance (Add Buddy, Send Message)
Yahoo! ID: petdance (Add User, Send Message)
Jabber: petdance@gmail.com

I'm Andy Lester, and I like to test stuff. I also write for the Perl Journal, and do tech edits on books. Sometimes I write code, too.

Journal of petdance (2468)

Tuesday September 03, 2002
05:36 PM

Using Perl for COBOL

[ #7506 ]
There was a job posting that came thru my inbox today for a company I interviewed with a year or two ago. The company name rang some nasty bells in my head.

This company did some records-tracking software in a truly mission-critical industry. I applied for the job, went down and talked to their head programmer guy. He did all the software himself. It's clear it was one of those "just get the guy to write it and get it working" situations. He wrote Perl as COBOL or BASIC. No use of any Perl string-handling, for example, much less objects or any other sort of post-1980s features.

And, it was all code like this:

$a = substr( $foo, 4, 3 ); print $a, " widgets found\n"; close BAR;
if ( $x == 3 ) { print "Do you want to bar?" } else { print
"Do you want to wango?" } open( FOO, "<$filename" ); $q = <FOO>;
# ... etc etc etc

He explained that he likes to put as much code on one line as he can so that he can see as much code as he can on the screen at one time. In Notepad, mind you.

I told him that if I came on board I could help them immensely, and that I would have to redo their entire way of doing things. He wanted a code-monkey to crank out some patches. He realized that we were not a fit. :-)

Now, this was two years ago, so I don't know what they're like now. It was easily the worst Perl I'd ever seen.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.