-- Leo's gemini proxy
-- Connecting to bbs.geminispace.org:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini; charset=utf-8
2023-08-07 · 9 months ago · 👍 ResetReboot, beetledjuice, naf
Regarding #1 I generally agree but I have found there are some cases where introducing a new module with some overlapping functionality actually reduces complexity and readability to such a degree that it is worth it. It was a hard learned lesson and it feels unintuitive but there is a balance to be struck here between de-duplication and complexity. The big problem ironically lies in changing the code when the code deduplication has created this web of dependencies if not done carefully.
The part about TDD was nice, and I imagine a lot of people have had similar experience. I didn't think much of it myself until I forced myself to give it a try and realized how many bugs I was catching along the way. What's more, they were being caught much closer to the call site, making debugging that much easier.
Nice article overall. Thanks for sharing.
The article gave me sort of a "I am a middle-aged, American white programmer, so listen to me, you inferior junior human being" attitude, that of course I do not particularly agree with.
I agree with others here that code duplication is not *always* bad. Programming is often about making tradeoffs. However, it is true sometimes that some decisions are made, when possibly thinking for a better solution for a couple of hours could have avoided it.
-- Response ended
-- Page fetched on Sun May 19 16:31:38 2024