4 ms·

> Trying to do this Next 12 -> Next 13 upgrade is not fun Oh, the horror! In all seriousness, I have been at this since the late 90s. 1996 specifically when

> Trying to do this Next 12 -> Next 13 upgrade is not fun Oh, the horror! In all seriousness, I have been at this since the late 90s. 1996 specifically when HTML/JS/CSS all became a thing. Do I want to write another complex dynamic HTML form with validation? Not really, no. I really don't enjoy it. Do I want to upgrade this current Angular application from 16 to 17 that I lead? Yes, I actually do. Because I know that will keep us from falling behind, from more tech debt, from an impossible upgrade path. Am I barking orders from on-high? No, I'm not. I'll actually do it myself, because I want to make sure we are are where we need to be. And after all these years, obviously the front-end is only the least of it. The APIs, the database, the custom hardware, the 3rd party vendors ... the ... Anyway, burnout is real, if you are feeling it, take a step back. But otherwise, I'd say with technology, you need to care about "new" otherwise you will fall behind.

dasil003 3y ago
Yeah this was my thought as well. If you’re paid to maintain software you have to actually do the work to keep up to date on its dependencies—that’s the job! We’ve seen the alternative play out countless times, GitHub forking Rails 2.3 and maintaining it for years and absorbing more and more tech debt for years until they bit the bullet and upgraded back to mainline Rails. Sure I’m getting old and it sometimes feels tiresome that software is a treadmill, but hey, it’s job security! And more importantly, change opens space for improvement, which feels good even if it doesn’t always live up to the promise.
- EMM_386 3y ago
  > Sure I’m getting old and it sometimes feels tiresome that software is a treadmill Precisely. Sometimes, I wonder if people are curious why after all these years am I apparently still working? Have I not become a "VP" or a "founder" or, better yet, a "VC"? To each their own. I'll be ok.

dasil003 3y ago

Yeah this was my thought as well. If you’re paid to maintain software you have to actually do the work to keep up to date on its dependencies—that’s the job! We’ve seen the alternative play out countless times, GitHub forking Rails 2.3 and maintaining it for years and absorbing more and more tech debt for years until they bit the bullet and upgraded back to mainline Rails. Sure I’m getting old and it sometimes feels tiresome that software is a treadmill, but hey, it’s job security! And more importantly, change opens space for improvement, which feels good even if it doesn’t always live up to the promise.

EMM_386 3y ago
> Sure I’m getting old and it sometimes feels tiresome that software is a treadmill Precisely. Sometimes, I wonder if people are curious why after all these years am I apparently still working? Have I not become a "VP" or a "founder" or, better yet, a "VC"? To each their own. I'll be ok.