distantsounds@lemmy.world to Bluesky@lemmy.worldEnglish · 2 months agocOdiNg eRroRlemmy.worldimagemessage-square55linkfedilinkarrow-up1513arrow-down17file-text
arrow-up1506arrow-down1imagecOdiNg eRroRlemmy.worlddistantsounds@lemmy.world to Bluesky@lemmy.worldEnglish · 2 months agomessage-square55linkfedilinkfile-text
minus-squarerekabis@lemmy.calinkfedilinkarrow-up42·2 months agoThere is no such ”coding error” that can cause omissions as specific and surgical as these. It was 100% intentional, plain and simple.
minus-squareFenrisulfir@lemmy.calinkfedilinkarrow-up21·2 months agoThe coding error was pushing the commits to the wrong branch and releasing to prod right away instead of waiting for the next big distraction first.
minus-squarepyre@lemmy.worldlinkfedilinkarrow-up14·2 months agothey think their constituents are stupid… … oh wait, they are.
There is no such ”coding error” that can cause omissions as specific and surgical as these.
It was 100% intentional, plain and simple.
The coding error was pushing the commits to the wrong branch and releasing to prod right away instead of waiting for the next big distraction first.
they think their constituents are stupid…
… oh wait, they are.
or an AI