Post AwfjZgTdPvdY3DNw1Y by CleyFaye@mastodon.top
 (DIR) More posts by CleyFaye@mastodon.top
 (DIR) Post #Awfi0yXCBjlbxuw77Y by ricci@discuss.systems
       2025-07-30T21:40:57Z
       
       0 likes, 0 repeats
       
       I have a problem with things that "save work". Some of them are great. Others are not.First, did the thing need to be done? Maybe, just maybe, it didn't and the best way to save work is just to not do it.Second, is there value in doing the thing? Did the person or people doing it learn something from it? Are they going to be better at it, or other things, or a more thoughtful person because they did it? Third, is the thing actually standing in the way of things we want more of? Or is it maybe the case that *other* things are in the way and this is the thing we want more of.Maybe think about these things before you decide whether the "work" needs to be saved.
       
 (DIR) Post #AwfjZgTdPvdY3DNw1Y by CleyFaye@mastodon.top
       2025-07-30T21:58:24Z
       
       0 likes, 0 repeats
       
       @ricci I'm not too sure because it's late, but it sounds somewhat similar to the sudoku's solver argument I often use. It's fun to *make* a sudoku solver software. Getting a pre-made one isn't fun. And the product is, ultimately, as useful as a book full of pre-filled crossword grids.Having a process that produce a sudoku solver faster with less work isn't that great.
       
 (DIR) Post #AwgxJ7xRaH6msHHs9o by gwozniak@discuss.systems
       2025-07-31T12:07:01Z
       
       0 likes, 0 repeats
       
       @ricci There is a similar argument I bring up all the time about "making things".