[ajmurmann]

The thing that stuck out the most to me in the resume is that he went to university to learn programming languages. That wouldn't happen today. Today you'd either get a book and definitely work through some online materials. How do you proof competency this way? You'll have to point at projects you did and talk a little more about what you did. I'm pretty sure that the set of potentially required skills has exploded. Knowing the right language seems to have been mostly it back then, the rest was likely proprietary to the company. I don't that they had yet another Fortran framework be popular every year. You didn't also need to know the correct test framework, scripting language, several markup languages etc.

While simpler times are attractive, I'm glad we have so much choice.

[kgwgk]

It does happen today:

https://extension.ucsd.edu/courses-and-programs/java-program...

https://www.pce.uw.edu/certificates/c-plus-plus-programming

https://www.uclaextension.edu/digital-technology/programming...

https://www.extension.harvard.edu/academics/professional-gra...

[williamscales]

I know that some of my friends from college went and did a 1-year CS masters program after their science degree. The curriculum was programming and basic CS fundamentals. I think this is pretty close to "going to university to learn programming languages" so I do think it still happens today. That said, I think the way of proving competency would still fall to projects because there are so many ways to take classes on programming these days that simply doing it doesn't mean you've learned anything.