Years before this guy got started, I was working in C. Then I moved onto more C, C++, then back to C. Today I'm working in a C++ codebase that compiles to C.
Lisp on the side, plus the Unix cruft that goes with build systems: shell, awk, make, ...
I went through the language churn as a kid. BASIC, assembly languages, Pascal, Modula-2. Studying CS pulled me into C world; all the upper level coursework at that time was systems programming in C on Unix, whether it be compilers, networking, distributed systems, operating systems or computer graphics or what have you.
I didn't think I'd be cranking out C for another 30 years after that, but I also didn't think of any reasons I wouldn't be.
Not everything I worked on is around; but the skills left behind are entirely relevant. There is hardly any technique I ever used that is inapplicable.
Lisp on the side, plus the Unix cruft that goes with build systems: shell, awk, make, ...
I went through the language churn as a kid. BASIC, assembly languages, Pascal, Modula-2. Studying CS pulled me into C world; all the upper level coursework at that time was systems programming in C on Unix, whether it be compilers, networking, distributed systems, operating systems or computer graphics or what have you.
I didn't think I'd be cranking out C for another 30 years after that, but I also didn't think of any reasons I wouldn't be.
Not everything I worked on is around; but the skills left behind are entirely relevant. There is hardly any technique I ever used that is inapplicable.