this post was submitted on 01 Oct 2023
57 points (100.0% liked)
Technology
37741 readers
63 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Doesn't it hurt those people a lot more when their project nearly inevitably gets shut down?
I'm still bitter about the project I worked on that got killed at my company three years ago.
Where I work we haven’t really shut down any projects in the last six years.
We’ve had some smaller projects which got parked due to shifting priorities, but other than that we’ve shipped everything else.
But inevitably, over a career in software there will be projects that don’t make it to production for one reason or another.
Personally I’m very pragmatic about it, but I know people who get very attached to the code they write.
I’m the kind of guy that is passionate about what I’m doing when I’m doing it, not necessarily for all eternity. I’ve written stuff that I’d be more than happy for someone to come and replace, but the thing about revenue generating systems (most people say “legacy”, but I prefer this term) is that they aren’t always easy to replace.
I know we’re not all wired that way, and some people find it harder to see an older system get retired. A consultant I use is more attached to my code than I am, for instance.