@shauna Oh, yeah, it's going to depend on a lot of things. One that I notice is the ecosystem you're in; if the language or platform or libraries you use are in a lot of churn, changing underneath your code, you have to make changes and updates just to keep it working and relevant. Running in place, so to speak. I've especially noticed this with NodeJS and Web apps using React, but I think there are other programming environments where this is the case, too.
Conversation
Notices
-
Embed this notice
Evan Prodromou 🇨🇦🇺🇸🇬🇷🇵🇸 (evan@cosocial.ca)'s status on Sunday, 15-Feb-2026 21:29:45 JST
Evan Prodromou 🇨🇦🇺🇸🇬🇷🇵🇸
-
Embed this notice
Shauna (shauna@social.coop)'s status on Sunday, 15-Feb-2026 21:29:46 JST
Shauna
Feels like this depends a lot on the project - how widely used is it, what life phase is it in (growth, maintainence mode, etc). If I personally am working on a one developer project it's probably just for me/for fun so I budget as many hours as is enjoyable. But other folks are able to solo maintain stuff other people actually want to use 😂
-
Embed this notice