Conversation

Notices

1. Embed this notice
   Eniko Fox (eniko@mastodon.gamedev.place)'s status on Wednesday, 03-Jun-2026 02:24:04 JST Eniko Fox

   i want smaller applications with fewer updates made by people who are paid more to produce less code and i'm not kidding

   • Rich Felker repeated this.
   • Embed this notice
     V (miss_rodent@girlcock.club)'s status on Wednesday, 03-Jun-2026 03:16:30 JST V

     in reply to

     @eniko Same, and also not kidding. I would rather have a group of three or four well-compensated maintainers who know the codebase very well (+ newer contributors they can afford to & have time to help teach/train) releasing security and bug fixes, with, maybe *one* feature release every year or two and a clear 'it's done'/feature complete state after which it's just bug fixes and maintenence/porting.

     Rich Felker repeated this.
   • Embed this notice
     me (me@social.jlamothe.net)'s status on Wednesday, 03-Jun-2026 03:19:29 JST me

     in reply to

     • Badtux the Snarky Penguin
     @badtux @eniko I've written software that was "finished" only to have to update it because an underlying library introduced a breaking change. I hate that.
   • Embed this notice
     Badtux the Snarky Penguin (badtux@mastodon.social)'s status on Wednesday, 03-Jun-2026 03:19:30 JST Badtux the Snarky Penguin

     in reply to

     @eniko But then the boss would have fewer people to manage, and be unable to justify his job. Most software changes are about employment for engineers, not necessity. Grr.

     As a software engineer I want computer languages and frameworks that stay stable for decades rather than have a new release every year that obsoletes old programs and requires a rewrite. But I don't get to have that :(.

     #software #softwaredevelopment

     Rich Felker repeated this.
   • Embed this notice
     V (miss_rodent@girlcock.club)'s status on Wednesday, 03-Jun-2026 03:20:44 JST V

     in reply to

     @eniko (Early on - like in alpha, when it's not even close to feature complete, then more feature updates is fine - but if at any point it hits a "Stable" release, I want that shit to be ACTUALLY stable - which means new features come slowly, and the priority is keeping it functional and reliable.)