TechCodex@programming.dev to Programmer Humor@programming.devEnglish · 1 year agoHours of workprogramming.devimagemessage-square40fedilinkarrow-up1830
arrow-up1813imageHours of workprogramming.devTechCodex@programming.dev to Programmer Humor@programming.devEnglish · 1 year agomessage-square40fedilink
minus-squareKalash@feddit.chlinkfedilinkarrow-up29·1 year agoI’m in the exact same boat right now. Also this change from 1:1 to 1:n entity was like one “minor” feature in a rather larger list of feature requests. It so far has caused more work then all the other features combined.
minus-squareAggressivelyPassive@feddit.delinkfedilinkarrow-up18·1 year agoAnd months later you’ll find out, that your change completely fucks over some internal optimizer statistic and causes the DB to turn into lava. I definitely don’t know that, because of several hour long outages and millions of lost revenue.
I’m in the exact same boat right now.
Also this change from 1:1 to 1:n entity was like one “minor” feature in a rather larger list of feature requests. It so far has caused more work then all the other features combined.
And months later you’ll find out, that your change completely fucks over some internal optimizer statistic and causes the DB to turn into lava.
I definitely don’t know that, because of several hour long outages and millions of lost revenue.