

There was something like
# sleep for about a second on modern processors
math.factorial(10000)
After it was found we left it in the code but commented out along with a sleep(1) for posterity.
Aka csm10495 on kbin.social


There was something like
# sleep for about a second on modern processors
math.factorial(10000)
After it was found we left it in the code but commented out along with a sleep(1) for posterity.


Yeah I hate when I read through a unit test and realize it doesn’t actually test anything other than itself.


I’ve thought about this wrt to AI and work. Every time I sit in a post mortem it’s about human errors and process fixes.
The day a post mortem ends with “well the AI did it so nothing we can do” is the day I look towards… with dread.


If you buy every single combination of numbers for the lotto, you can’t lose.
Special shout out to the person who committed a gigabyte memory dump a few years ago. Even with a shallow clone, it’s pretty darn slow now.
We can’t rewrite history to remove it since other things rely on the commit IDs not changing.
Oh well.


Upvoted. This is something I learned rather recently. Sometimes it’s more performant to slowly leak than it would be to free properly. Then take x amount of time to restart every n amount of time.


The UI goes in circles. I wish we stopped changing things when they aren’t broken.


I guess if it was a daily unlimited good pizza party instead of a small raise given as long as I had the job; then maybe it would be a better deal.
If I’m either getting an extra $100 a month or $20 of pizza every day… I think pizza wins.
What are the chances we get daily free pizza?
If it’s not daily: I’d take the money. If daily: I’d have to think about it.
If you read this far and it’s not clear: I’m joking.


I actually like the ability for a local AI to help with this in theory. I don’t think it’s an excuse for unintuitive UIs though.


For something end-user facing: I could understand this argument.
In this case they were more or less just calling a C function that had an unsigned long long as the parameter they were setting negative.
The whole ‘bug’ was that the other side of the function call was seeing a positive number no matter what.
The real situation was a bit more complicated, but that’s the gist.


I once had a QA engineer file a bug saying they couldn’t do negative testing since negative numbers were converted to positive.
The function took an unsigned integer. Took a lot of explaining to get them to understand that negative testing isn’t necessarily negative numbers.
Bottom left made me miss Kmart

A true shitpost.


Through the magic of make, you can write code that changes if statements to while loops then changes it back after compilation passes or fails.
I only give good advice.


I’d be down for a smart watch with like a week of battery life, with a backlight on lift, and I guess NFC for paying.
I know I won’t get that combo, but I can dream.
It’s been too many years since I’ve played on a tire swing.


Makes me think that platforms banning Trump after Jan 6 were just kissing up to Biden coming in. Maybe there is just a cycle of capitalist sucking up.


+1.
I wish we had type c but all cables were labeled with clear functionality from the start. I don’t like data/power only cables.


I’m guessing this is a cost thing. You don’t need to pay for fact checking anymore.
… still obnoxious and pushing us towards a dead echo chamber internet. Get ready for AI personalities voting on community notes.
The real pros don’t even link or connect them. You have to know the others exist.