3 ms·

> No reason to act like this. Not the author of the parent comment; but with bristling replies like this, aren’t you dismissing the experience of those who, th

> No reason to act like this. Not the author of the parent comment; but with bristling replies like this, aren’t you dismissing the experience of those who, through years of experience, have become weary, and disillusioned, and a bit cynical? Isn't it also a valuable perspective (don't go for the new and shiny; stick with the tried and true), delivered in exactly the same way many older craftsmen have historically shared their knowledge with the younger and more enthusiastic ones?

zinclozenge 7y ago
There are plenty of reasons to learn new languages and frameworks. Dismissing them because of 'new and shiny' is not a good reason.
- azangru 7y ago
  Sure, but this is the objection to the substance of the response, not the way it is delivered (which is what the parent comment is unhappy about).
- tracer4201 7y ago
  The only reason to learn most of these frameworks is if your line of work has a high chance you’d inherit, need to support, and/or build new features on top of such a code base. Otherwise, we don’t need 10 different tools for building—what is at the end of the day—a simple website or CRUD application. Complexity isn’t a good thing. Creating complexity is the first sign of inexperienced coders.
  - SahAssar 7y ago
    One good reason is to learn different ways of doing things. I think the best way to understand why something is the way it is is to look at different ways it could be done and what are the pro/cons of it. I've seen many times that trying and understanding a new framework leads to me implementing something in a better way in a framework I was already using.
- rumanator 7y ago
  > Dismissing them because of 'new and shiny' is not a good reason. How about putting a pin on technologies that are unproven and immature? Because many projects (and careers) have died a painful death because an overeager developer decided to bet the farm on a shiny flavor of the month because it was trending.
SahAssar 7y ago
There is a way to write a comment about what is great about tried and true tech without assuming peoples age or talking down about new tech as a whole. I'm in mostly the same camp as the parent in that I prefer solutions that are proven over years instead of the latest shiny thing, but new tech also brings a lot of interesting ideas to implement in a "proven over time" stack.

zinclozenge 7y ago

There are plenty of reasons to learn new languages and frameworks. Dismissing them because of 'new and shiny' is not a good reason.

azangru 7y ago
Sure, but this is the objection to the substance of the response, not the way it is delivered (which is what the parent comment is unhappy about).
tracer4201 7y ago
The only reason to learn most of these frameworks is if your line of work has a high chance you’d inherit, need to support, and/or build new features on top of such a code base. Otherwise, we don’t need 10 different tools for building—what is at the end of the day—a simple website or CRUD application. Complexity isn’t a good thing. Creating complexity is the first sign of inexperienced coders.
- SahAssar 7y ago
  One good reason is to learn different ways of doing things. I think the best way to understand why something is the way it is is to look at different ways it could be done and what are the pro/cons of it. I've seen many times that trying and understanding a new framework leads to me implementing something in a better way in a framework I was already using.
rumanator 7y ago
> Dismissing them because of 'new and shiny' is not a good reason. How about putting a pin on technologies that are unproven and immature? Because many projects (and careers) have died a painful death because an overeager developer decided to bet the farm on a shiny flavor of the month because it was trending.

SahAssar 7y ago

There is a way to write a comment about what is great about tried and true tech without assuming peoples age or talking down about new tech as a whole. I'm in mostly the same camp as the parent in that I prefer solutions that are proven over years instead of the latest shiny thing, but new tech also brings a lot of interesting ideas to implement in a "proven over time" stack.