Comment It doesn't have to. (Score 1) 80
Going from bits/OP-code to OOP and Functional Programming easily happen on its own in a single individual lifetime and career if the hardware is there and available. Many people doing programming in the 80ies or eariler discovered some form of OOP on their own just by writing code. The first serious refactoring of the first seriour program usually leads to OOP all by itself. I clearly remember discovering fundamental principles like higher PLs, APIs, OOP, information hiding, state management, event / messaging systems and other fundamental principles on my very own before learning the academic terms of those things that others had discovered and named. I even came up with my version of Oauth/OIDC for only after something like two weeks to think: Wait a minute, I sure has hell can't be the only and/or first one to come up with the principle of the Ident/Auth/Auth triangle. And sure enough, Oauth and it's update OIDC is already standardized and documented. Test First or DBC are also things that come naturally once you've written a few non-trivial pieces of code that grow beyond the scope of what a single human brain can keep track of all at once at the same time.
Bottom line: No need for those traditions to survive, they come back naturally for any healthy brain capable of logic with a sufficient enough logic machine to tinker with at it's hands.
And let's be honest: For some of the historically grown mess in IT (just take a look at the keyboard in front of you) it would actually be a good thing for that to get lost and be reinvented.