Conversation

Notices

1. :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans: (allison@hidamari.apartments)'s status on Friday, 12-Apr-2024 02:03:12 JST :blobancap: :blobcattrans: :blobancap: :blobcattrans: :blobancap: :blobcattrans:

   • CrunkLord420
   @crunklord420 it would have hit better if it were some catastrophic gnome issue instead
   •  (mint@ryona.agency)'s status on Friday, 12-Apr-2024 02:03:11 JST 

     in reply to

     • CrunkLord420
     @allison @crunklord420 :ebussy: What's the use case for code quality?
   • That Would Be Telling (thatwouldbetelling@shitposter.world)'s status on Friday, 12-Apr-2024 02:33:47 JST That Would Be Telling

     in reply to

     • 
     • CrunkLord420

     @mint @crunklord420 @allison An idiot's question of course.

     Back in the day, when OOSE was the published source and use case analysis was becoming a thing, it was noted, I think in the original book? That this method won't reveal the need for a roof in a house, it's not something you use. Ditto code quality, until a lack of it makes it too expensive in time and/or money to modify.

     (Lately people have tried to reconceptualize this as "technical debt," but with for example the US Federal government going a trillion dollars more into debt every three months I think that's a very hard sell.)

      likes this.