> looking at the "new trend" (ex Angular, React and NodeJS) as unnecessary
Well, I know that you were just throwing out a random example, but... I wouldn't be so quick to dismiss Angular and React. They're actually pretty good, pretty clever solutions to some of the problems the plague web application developers, and help us get a long way to a flexible web environment. Even Node.js may seem "wrong" to those of us whose first experience with a computer was a command-line terminal, but people were saying that Java on the server side was unrealistic 15 years ago. And really, there is a benefit to using the same language on the server as on the client, especially as those two drift closer and closer together.
The problem I see is that the "new devs" (and their 20-year-old "startup founder" bosses) assume that Angular, React and NodeJS, being the new, trendy, hip thing, is all there is and all you need to know. As long as you know those fairly well, the thinking goes, you don't need to know anything about TCP/IP, HTTP, SSL, bash, signals, processes, threads... all the things that us old fogeys have spent decades wrestling with. I recently watched a (much younger) colleague of mine reject a candidate because he was misusing the term "route". I asked "you mean like a TCP source route? That's not really that relevant to the UI position he was interviewing for." He seemed incredulous that I didn't "know" that "route" was an "industry-standard" term for a URL (apparently that's what Node.js's Express framework calls URLs - hint, the term "route" never appears in RFC 2616, which actually specifies HTTP). THAT mentality is the frustrating one, and it's all over the place.
Well, I know that you were just throwing out a random example, but... I wouldn't be so quick to dismiss Angular and React. They're actually pretty good, pretty clever solutions to some of the problems the plague web application developers, and help us get a long way to a flexible web environment. Even Node.js may seem "wrong" to those of us whose first experience with a computer was a command-line terminal, but people were saying that Java on the server side was unrealistic 15 years ago. And really, there is a benefit to using the same language on the server as on the client, especially as those two drift closer and closer together.
The problem I see is that the "new devs" (and their 20-year-old "startup founder" bosses) assume that Angular, React and NodeJS, being the new, trendy, hip thing, is all there is and all you need to know. As long as you know those fairly well, the thinking goes, you don't need to know anything about TCP/IP, HTTP, SSL, bash, signals, processes, threads... all the things that us old fogeys have spent decades wrestling with. I recently watched a (much younger) colleague of mine reject a candidate because he was misusing the term "route". I asked "you mean like a TCP source route? That's not really that relevant to the UI position he was interviewing for." He seemed incredulous that I didn't "know" that "route" was an "industry-standard" term for a URL (apparently that's what Node.js's Express framework calls URLs - hint, the term "route" never appears in RFC 2616, which actually specifies HTTP). THAT mentality is the frustrating one, and it's all over the place.