Recovering interrupter with occasional relapses, lover of spreadsheets, blogger, programmer, adept debugger, conjurer of analogies, and probably other things.
I'm not the original poster, but what I've found is that there's a tendency to chase the new thing. And as such, a person loses the opportunity to reflect on the impact of what they've done. Each new thing attempts to solve the problem of the previous new thing, but itself introduces a new problem as it specifically address the previous old problem (but might have forgotten the lessons of what the previous new thing fixed).
In other words, our collective understanding of software is soft and shifting, and we're forgetting the lessons that each technology solved.
tl;dr - move fast and break things is terrible for the human condition.
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.
I'm not the original poster, but what I've found is that there's a tendency to chase the new thing. And as such, a person loses the opportunity to reflect on the impact of what they've done. Each new thing attempts to solve the problem of the previous new thing, but itself introduces a new problem as it specifically address the previous old problem (but might have forgotten the lessons of what the previous new thing fixed).
In other words, our collective understanding of software is soft and shifting, and we're forgetting the lessons that each technology solved.
tl;dr - move fast and break things is terrible for the human condition.