Agent641@lemmy.world to Programmer Humor@programming.dev · 3 days agoClock but we saved DB space by just returning the index of the array of DigitNameslemmy.worldimagemessage-square38linkfedilinkarrow-up1282arrow-down110
arrow-up1272arrow-down1imageClock but we saved DB space by just returning the index of the array of DigitNameslemmy.worldAgent641@lemmy.world to Programmer Humor@programming.dev · 3 days agomessage-square38linkfedilink
minus-squaretyler@programming.devlinkfedilinkarrow-up4·1 day agodeepseek v3.1 had an (almost) perfect clock once for me.
minus-squareDerpgon@programming.devlinkfedilinkarrow-up1·10 hours agoDid it show the correct time? Did it tick correctly? From my observations, even clocks that looked okay had like wrong second speed, swapped hour and minute, or was rotated altogether.
minus-squaretyler@programming.devlinkfedilinkarrow-up1·6 hours agoYeah it was showing the correct time and right tick speed. But it was only one of the clocks on that model. The rest were wrong.
minus-squaretyler@programming.devlinkfedilinkarrow-up1·7 hours agoYeah it was showing the correct time and right tick speed. But it was only one of the clocks on that model. The rest were wrong.
deepseek v3.1 had an (almost) perfect clock once for me.
Did it show the correct time? Did it tick correctly? From my observations, even clocks that looked okay had like wrong second speed, swapped hour and minute, or was rotated altogether.
Yeah it was showing the correct time and right tick speed. But it was only one of the clocks on that model. The rest were wrong.
Yeah it was showing the correct time and right tick speed. But it was only one of the clocks on that model. The rest were wrong.