They say amongst the admins the system's okay
If you get it set up and work on your way
But as a code writer such prospect is grim
if the code is piss poor and the bugs can't be seen

Cracking show - it did compile
But I still need to checkl up the debugging file

They taught me with Pascal on how to write code
With arrays and pointers and strong types and node
Forgot to free all those used pointers with NEW
All too late I found out how the CPU load grew

From Pascal then into the C stuff I went
To find out that language is quite badly bent
It uses weak typecast and allows overflows
with so many ways to screw up God only knows

I thought I had checked out the pointers - compiled
when with a core dump my process promptly died
After eight hours I had debugged the code
It's hell of a job and I got brain overload

I write for the money, I write for just fun
And I'm awfully anxious to get the code done
But for debugging session at midnight in dark
I'll tell boss in morning "Blow that for a lark".

Now Perl with the Toolkit is remarkably sound
It does not need pointers, just arrays are found
Writing those Windows programs is just fun
You can port code on Linux and get the things done

There's an ongoing fight between Java and C
As I write with VB, I just cannot see
why the engineers fight o'er which language is best
just stick on what you master and leave all the rest

So come all young techies and listen to me,
A code-writing egghead you never should be
But learn yourself skills that an admin will need -
and be just as happy as an admin can be