popcar2@programming.dev to Programmer Humor@programming.devEnglish · 7 months agoWe'll refactor this next year anywaysprogramming.devimagemessage-square50fedilinkarrow-up1783arrow-down110
arrow-up1773arrow-down1imageWe'll refactor this next year anywaysprogramming.devpopcar2@programming.dev to Programmer Humor@programming.devEnglish · 7 months agomessage-square50fedilink
minus-squareswordsmanluke@programming.devlinkfedilinkarrow-up5·7 months ago Just saying. … Saying what, exactly? I said that we should design for change “within reason” because we can’t know what exact changes are needed. And you argued… The same thing? Just in the reverse order?
minus-squareSerinus@lemmy.worldlinkfedilinkarrow-up1·7 months agoSeems like he’s worried you’ll Java everything up, which can be valid. I think a good, easy example is whether your application should allow a selection of databases or be tied to one database. You can make arguments for either, often (but not always) regardless of your use case.
… Saying what, exactly?
I said that we should
And you argued… The same thing? Just in the reverse order?
Seems like he’s worried you’ll Java everything up, which can be valid.
I think a good, easy example is whether your application should allow a selection of databases or be tied to one database.
You can make arguments for either, often (but not always) regardless of your use case.