That's interesting. I am actually not an American and just moved to the US a couple of months ago. But I hadn't heard that take before. So I have to admit, I have had no appreciation for that scenario. Generally, you think you are making things better every time you discover a new way to improve performance, improve tooling, or find an easier abstraction. Then again I've spent most of my professional career working on small teams developing a single product over the course of several years. In that scenario after maintaining something for a decade you tend to think a lot about the limitations of the original system, and how you'd do it differently next time.
And a lot of this article was reflecting on the team making this switch when we finally retired the old system (May 2011-Dec 2020). Ironically it was this same experience that lead me to writing my own UI library, initially hoping to improve development at the company. I guess it's just a matter of perspective. I saw the experience as an opportunity. Ironically as much as I still dislike TypeScript, it was unanimous that it was the way to go. That's with myself from Canada, a lead front end dev from Spain, a junior front end dev from Japan, a backend dev from Korea, a senior backend dev from France, a devops engineer from Bulgaria, and a QA lead from the UK.
But I haven't had the distinct pleasure of maintaining someone else's code for years. Everyone was excited to work on our project. So I probably can't appreciate the scenario where you are basically being forced to learn the latest greatest thing long after it is considered so. I definitely had to slog through decade old open source projects, but when it came time to finally lay that beast to rest we got to choose what we used. And TypeScript one of them.
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.
That's interesting. I am actually not an American and just moved to the US a couple of months ago. But I hadn't heard that take before. So I have to admit, I have had no appreciation for that scenario. Generally, you think you are making things better every time you discover a new way to improve performance, improve tooling, or find an easier abstraction. Then again I've spent most of my professional career working on small teams developing a single product over the course of several years. In that scenario after maintaining something for a decade you tend to think a lot about the limitations of the original system, and how you'd do it differently next time.
And a lot of this article was reflecting on the team making this switch when we finally retired the old system (May 2011-Dec 2020). Ironically it was this same experience that lead me to writing my own UI library, initially hoping to improve development at the company. I guess it's just a matter of perspective. I saw the experience as an opportunity. Ironically as much as I still dislike TypeScript, it was unanimous that it was the way to go. That's with myself from Canada, a lead front end dev from Spain, a junior front end dev from Japan, a backend dev from Korea, a senior backend dev from France, a devops engineer from Bulgaria, and a QA lead from the UK.
But I haven't had the distinct pleasure of maintaining someone else's code for years. Everyone was excited to work on our project. So I probably can't appreciate the scenario where you are basically being forced to learn the latest greatest thing long after it is considered so. I definitely had to slog through decade old open source projects, but when it came time to finally lay that beast to rest we got to choose what we used. And TypeScript one of them.