tl;dr, latest tech trends are worth watching but generally investing into the latest trends often is not going to yield a return on investment, waiting on maturity and/or for the next generation is often a better decision.
I like to skip a generation of tech, I keep my eye on it but it has proven me well over the course of my career. When we talk about programming languages and frameworks, the trends come and go. There are times when a newer trend makes sense in that it solves a specific problem for you. Remember when scala was all the rage but now it's rarely discussed but rather you hear about rust. Then there was ruby [on rails], in which the industry shifted towards ruby on rails but now the vast majority of that has moved over to javascript/typescript in node.js.
When we're talking about programming practices / infrastructure / etc, there are similar trends.. monolith vs. micro service. Both have their advantages and disadvantages but more often than not the monolith has often won out unless a specific use case makes the micro services worthwhile.
I liken this to the evolution of how server computing has changed over the years and evolved. bare metal -> bean counters -> kvm -> docker / kubernetes -> serverless (faas). Often, I've skipped a generation, it's not to say the intermediary generation was not useful but often times the next generation is built upon the shoulders of the generation prior and skipping a generation affords you the ability to focus more in-depth and buck the trend rather than cycling back and forth on items.
Many times we need to do more research from a fundamentalist point of view rather than deeply vesting ourselves in the ever changing landscape of languages, frameworks, tools, infrastructure, etc. If we focus on the needs of what our solution needs to bring and looking for solutions to specific problems, oftentimes we will naturally gravitate to where our needs are best solved. Sometimes that is the latest and greatest but often times it's not necessary to adopt the latest trends.
Now, not to completely toss out new trends.. they should be followed as the industry and shift along with job candidates. If you want to be able to hire, you also need to be aware that certain trends are going to be easier to hire for... if you're a super early adopter of new programming languages and/or frameworks, your hiring pool is only going to shrink, likewise, if you never adopt new tech and are programming in fortran you're not going to find many qualified candidates that are available for the position.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
tl;dr, latest tech trends are worth watching but generally investing into the latest trends often is not going to yield a return on investment, waiting on maturity and/or for the next generation is often a better decision.
I like to skip a generation of tech, I keep my eye on it but it has proven me well over the course of my career. When we talk about programming languages and frameworks, the trends come and go. There are times when a newer trend makes sense in that it solves a specific problem for you. Remember when scala was all the rage but now it's rarely discussed but rather you hear about rust. Then there was ruby [on rails], in which the industry shifted towards ruby on rails but now the vast majority of that has moved over to javascript/typescript in node.js.
When we're talking about programming practices / infrastructure / etc, there are similar trends.. monolith vs. micro service. Both have their advantages and disadvantages but more often than not the monolith has often won out unless a specific use case makes the micro services worthwhile.
I liken this to the evolution of how server computing has changed over the years and evolved. bare metal -> bean counters -> kvm -> docker / kubernetes -> serverless (faas). Often, I've skipped a generation, it's not to say the intermediary generation was not useful but often times the next generation is built upon the shoulders of the generation prior and skipping a generation affords you the ability to focus more in-depth and buck the trend rather than cycling back and forth on items.
Many times we need to do more research from a fundamentalist point of view rather than deeply vesting ourselves in the ever changing landscape of languages, frameworks, tools, infrastructure, etc. If we focus on the needs of what our solution needs to bring and looking for solutions to specific problems, oftentimes we will naturally gravitate to where our needs are best solved. Sometimes that is the latest and greatest but often times it's not necessary to adopt the latest trends.
Now, not to completely toss out new trends.. they should be followed as the industry and shift along with job candidates. If you want to be able to hire, you also need to be aware that certain trends are going to be easier to hire for... if you're a super early adopter of new programming languages and/or frameworks, your hiring pool is only going to shrink, likewise, if you never adopt new tech and are programming in fortran you're not going to find many qualified candidates that are available for the position.