←back to thread

Good Software Development Habits

(zarar.dev)
361 points mmphosis | 2 comments | 17 Nov 24 16:34 UTC | HN request time: 0.632s | source
Show context
leetrout ◴[17 Nov 24 18:05 UTC] No.42165704[source]▶
> It's better to have some wonky parameterization than it is to have multiple implementations of nearly the same thing. Improving the parameters will be easier than to consolidate four different implementations if this situation comes up again.

Hard disagree. If you cant decompose to avoid "wonky parameters" then keep them separate. Big smell is boolean flags (avoid altogether when you can) and more than one enum parameter.

IME "heavy" function signatures are always making things harder to maintain.

replies(17): >>42165868 #>>42165902 #>>42166004 #>>42166217 #>>42166363 #>>42166370 #>>42166579 #>>42166774 #>>42167282 #>>42167534 #>>42167823 #>>42168263 #>>42168489 #>>42168888 #>>42169453 #>>42169755 #>>42171152 #
urbandw311er ◴[17 Nov 24 23:23 UTC] No.42168263[source]▶
Why have we started “hard” disagreeing with each other recently? What’s wrong with just disagreeing?
replies(2): >>42168342 #>>42168907 #
1. internet101010 ◴[18 Nov 24 01:27 UTC] No.42168907[source]▶
Difference between the two is that hard disagree means you won't be able to change their mind.
replies(1): >>42170577 #
2. eonmist ◴[18 Nov 24 07:50 UTC] No.42170577[source]▶
Or "should not" change their mind. If I hard disagree, then I should not change my mind, because I see no valid reason, and both my experience and reasoning are solid to the degree I am certain the arguments presented can not develop into a valid reason to change my mind. "Hard disagree" may signify being certain. I then am responsible, for my own sake and wellbeing, of being right in relation to reality, or reality will simply hard disagree.