3 ms·

I don't know if there's a term for this, but never updating your tooling also keeps a potential door closed. During my first internship, we never changed the s

I don't know if there's a term for this, but never updating your tooling also keeps a potential door closed. During my first internship, we never changed the stack. When I ran in a problem, it was because either - we needed to bump major vers - it's too new of a feature and the library isn't actively maintained In my current job, worst case it's just not a stable feature yet and we need to wait. Both situations need a workaround, but I get a lot more motivated if I get the feeling we're "on-edge" of a tool.

bronlund 2y ago
Yes, It's kind of the same with me. We are stuck in a lot of legacy code and trying to upgrade a package more often than not, results in us having to roll it back because it breaks so much other stuff. We know we have to start from scratch at some time, but we want to make it as future proof as possible - seeing what a huge codebase looks like after a decade of fixes :)