
Don Spang says: I once found myself winging it in a job interview and somewhat exaggerated my technical experience in the field of mainframe computer operations. 24 years later, I'm still there. Ever had to improvise to get by? Tell us you tales of MacGyver-type genius.
( , Thu 28 Mar 2013, 12:31)
« Go Back | See The Full Thread

It doesn't matter how many times you write scripts, the minute you stop programming perl it all becomes gibberish again. The best strategy is to decompose your code into the steps you want it to do and then google for code snippets that do each one.
( , Fri 29 Mar 2013, 19:28, 2 replies)

I tried to cobble together some Perl after a gap of around 6 years, and failed to achieve anything even after using the internet and all.
( , Fri 29 Mar 2013, 22:50, closed)

Stages of writing a perl script
1 - Write code
2 - Don't bother commenting it - you'll remember what it does no problem
3 - Go back to it next day and realise you have no idea what it does
4 - Rewrite code
5 - Loop
( , Sun 31 Mar 2013, 14:00, closed)

Here's a code snippet of APL:

Even better, our system was the world's only functioning multi-threaded real-time APL.
Perl? Amateurs.
( , Tue 2 Apr 2013, 13:34, closed)
« Go Back | See The Full Thread