I read in your SQL article that you had never used pointers in your life, or never needed to. But you also mention that you used Perl. This means you have in fact used pointers and absolutely must in Perl, unless you never used anything as complicated as an array/hash of arrays/hashes.
Larry Wall and co. call their pointers "references", either because they didn't know the difference or because of the bad reputation of pointers. But the fact is, a pointer and a reference both point to a location in memory. The difference between the two is that a pointer makes you "take the address of" a variable to get it and do some kind of casting/"dereferencing" to use the data again, while a reference handles all this for you (even in C++).
This is one of the biggest reasons Perl has such ugly, hard to read/write/teach syntax (how many newbies don't understand how to pass two arrays to a function?). And what is worse, they keep pointers in Perl 6. They just add more magic syntax to try and keep them out of everyone's way.
This is a good point!
In that case, I've not only used pointers, I've used them extensively, overused them, gone far out of my way to use them, and even found ways to work around their absence in Ruby.
I disagree with the criticism, though. Anonymous references are absolutely the part of Perl I enjoy the most. I find it very limiting when a programming language expects you to name all your variables. It's much nicer when you can write code to name the variables for you.