This does of course lead up to the question: what counts as a programming language?
That's actually a good question. Is sh (including ksh, csh, bash, ...) a programming language? It can be: I've seen programs that are tens of thousands of lines long in a single script, with layers and layers of functions, variables, and so on. On the other hand, someone who types "ls" at the prompt is not writing a program. And I'm not sure that a 5-line script (perhaps with an if or for statement) is a "program".
The same question applies for example to awk: the awk 1-liners that many people put in their shell script (often just "{print $5}" to print the fifth column) are not really programs. On the other hand, one can write programs that are complex and hundreds of lines long in awk (been there, done that).
I think to count something as a "programming language one uses", the programs one writes have to have some minimum complexity. Following Dijkstra's old saying, I would set that limit at the point where the program is complicated enough that it might have a bug (Dijkstra's saying is something like "there are two kinds of programs: those that are so short that they obviously have no bug, and those that are so long that they have no obvious bug.
A related question is whether a purely descriptive language can be considered a programming language. For example, the file
/etc/rc.conf on a FreeBSD system that has lots of stuff installed might be hundreds of lines long. It represents a heck of a lot of work, and has taken weeks to get every detail right. Yet, it is not a program, only a collection of settings for other programs. Similarly, lex and yacc inputs are not programs in themselves (they only tell lex and yacc how to spit out a parser that does the job), but they are complicated, and hard to write.
And about being an old-timer: I've made money programming in RPG-II (not much), and in COBOL (quite a bit). A few years ago I discovered that there is now a Gnu COBOL compiler, so for fun I installed it, and spend an hour writing a short COBOL program that actually did some useful work for me. Amazingly enough, with quite a bit of help from the web (I had forgotten much of the syntax), it worked. And completely obviously, it reminded me what a horrible language COBOL was, and how much better we have it now: the same task could have been done in Python or Perl in 2 minutes.