Maynard

@Quelklef

milk consumer

maynards.site/

girly but not a girl

name-color: #C09

Maynard @Quelklef8/30/2023, 9:43 PM

becoming more patient and finding more pleasure in rote tasks

not sure how i feel about it. impatience historically has been a pretty big factor for me pushing discovery and creativity

for instance when programming. if i have a system with many units. and adding a unit requires some boilerplate. and i enjoy the process of writing that boilerplate. then i will never desire discovering the abstraction to remove it

more concretely, if i don't mind writing toJson() and fromJson() on all my types, i would never discover deriving (Generic, ToJson)

You must log in to comment.

in reply to @Quelklef's post:

Kristin Rutenkolk @wiredaemon8/30/2023, 10:21 PM

Sometimes the abstraction needs also to be justified I would say. Imho we don't abstract for the fun of it, but because it improves some non-functional property (like maintainability). I don't think rote tasks / boilerplate code / etc. is bad as long as its alternative doesn't noticeably improve the non-functional properties we actually care about.

Maynard @Quelklef8/31/2023, 8:21 PM

that's true!

i think we could replace "pleasure in rote tasks" in my post with "high tolerance for poor codebase qualities" (eg maintainability) and it'd still be true

eg. more patience -> more patience fixing preventable bugs -> less drive to find such a prevention

Kristin Rutenkolk @wiredaemon9/1/2023, 7:05 AM

Ok, yeah. I see now. That makes a lot of sense to me :eggbug:

edit: would it be fair to say you want to have no patience for bad code (like, whatever that means in any context)? But you notice yourself developing it?

Maynard @Quelklef9/1/2023, 9:18 PM

i think i have low tolerance for code that feels like it could be better. generally speaking, if i think it could be better (ie, there's an abstraction hiding) i immediately want to find it

that said i don't always follow that urge, as abstracting is hard and not always worth it

Pinned Tags