> Wouldn't this value experience and knowledge (like everything you learned in university) at zero?
Having switched professions twice, I now use practically nothing of what I learned in university from about second year forward. Math and to some extent physics are still relevant, but that's pretty much it.
It might be painful to admit, but the practical value of that rather specialized knowledge that took me several years of hard work to obtain is pretty much zero now.
> It might be painful to admit, but the practical value of that rather specialized knowledge that took me several years of hard work to obtain is pretty much zero now.
It's sad that your professors didn't tell you beforehand that you were going to learn how to learn during that time, not just study a particular technology stack.
The short answer is probably no. And the fact is that top universities mostly aren't so focused on teaching whatever language or framework is the flavor of the day.
That said, you need tools of some sort if you're going to actually build things as opposed to just learning, say, algorithms in pseudo-code. And it probably makes sense to use some fairly standard language to do so. There's not much point in making things deliberately obscure by making students use some language that the professor designed for his PhD thesis.
I bet it wasn't a total waste. The real point of school, particularly university, is to learn how to learn rather than learn a bunch of facts or tools. Attending university probably made it a lot easier for you to switch professions twice.
Having switched professions twice, I now use practically nothing of what I learned in university from about second year forward. Math and to some extent physics are still relevant, but that's pretty much it.
It might be painful to admit, but the practical value of that rather specialized knowledge that took me several years of hard work to obtain is pretty much zero now.