Time flies while you're having fun, but then one day your bio says something about being a 30+ year veteran in software engineering. Still, I've not seen it all, let alone done it all (yet).
Even the "worst" language is worth studying (if not learning), so as to appreciate why its bad. And maybe why it's not.
(Let's exclude esoteric languages, because they are designed to be "bad", and its trivial to understand why that are bad. In this regard, they are fun, but not interesting).
In less black-and-white terms, I'm tired of developers telling me that, for example, functional programming is not relevant, but who have never actually bothered to study it.
The more you learn (or at least study), the more informed your opinions will be. As a software development professional, you have duty to inform your opinions.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
Even the "worst" language is worth studying (if not learning), so as to appreciate why its bad. And maybe why it's not.
(Let's exclude esoteric languages, because they are designed to be "bad", and its trivial to understand why that are bad. In this regard, they are fun, but not interesting).
In less black-and-white terms, I'm tired of developers telling me that, for example, functional programming is not relevant, but who have never actually bothered to study it.
The more you learn (or at least study), the more informed your opinions will be. As a software development professional, you have duty to inform your opinions.
Exactly. It takes a lot of time to realize that there is no right answer and that everything is a question of context and of trade-offs.
@daedtech is really good on this here Coders in the Hands of a Missing God: How Newly Minted Freelancers Badly Miss the Point