Employer: Major Utility in the SE United States. Job: Mostly, kick dead whales down the beach; that is, help keep an old SCADA system running while helping to implement another vendor's replacement. Occasionally I get to code. Over the last 30+ years have done useful work with IBM Exec, Exec2, Rexx, Fortran, APL (though long forgotten), C, (n)awk, ksh, TCL/Tk, Java, PL/SQL and lately, Perl. Never had much use for fingernail clippings in oatmeal (l)anguishes, with the exception of Scheme, which I once aspired to learn when a much younger man. { And TCL, which I don't really think deserves the label }. I still think tail-end recursion as iteration is a cool thing that every language should support, especially a one as cool and often magical as Perl. I plan on doing great things with Objective-C, eventually, but not this year, as it looks like I'll have to focus on more practical endeavors, mostly in C, ksh, nawk, Pascal (yes, Pascal, and that is on the NEW system), PL/SQL, Java and HALLELUJAH Perl. Confession: I avoided Perl, railed against it and cast dispersions on it rather constantly and confidently for over fifteen years. Once about 10 years ago, i decided to "bite the bullet" and learn it, but was dissuaded anew by of all things "Programming Perl" itself, when it spoke of problems with reentrancy of the code that supported event handlers, not to mention all the little idiosyncrasies inherent in a "grown" language... This caused me to recant my nascent enlightenment and return to the wilderness of KSH, c and nawk (like nawk can handle interrupts any better...) and wander there for several years. Recently I returned to the light and now wonder how I could have been so foolish. Perl's handing of binary data in strings alone would have repaid me for any pain suffered due to Perl's quirks... ... Oh well, I'm home now.