deleted by creator

You press c and t using the same finger, and i with another. So since you need to use the same finger twice in a row, also moving it a fair distance in between, your other finger just presses the button a little bit too soon, and that’s how you end up with funciton

Yeah, been there. The codebase I worked on also had a single method with 10k lines.

The database IDs were strings including the hostname of the machine that wrote to the DB. Since it was a centralized server, all IDs had the same hostname. The ID also included date and time accurate to the millisecond, and the table name itself.

Me: Mom, can we have UUIDs? Mom: We have UUIDs at home UUIDs at home: that shit

It really just boils down to what you’re trying to do. Which is why choice is good, as always

Yes, that is how you’d use a wrench in that context

The final hour is 8, and it would be pointing at the end of that. I don’t see your problem.

Except this is order by DESC, so the ‘lowest’ value (Two) goes on index zero, the second lowest (Twelve) goes on index 1, etc.

Idk to me the top position is index 0, even though it’s labeled 12.

Think about it this way: when a new day begins, where are the clock hands?

I guess stuff like desktop widgets might be a candidate. Not sure if there’s a specific framework for those, though

Why not both?

depends. if you’re rounding, yeah. I was just thinking of truncating.

I guess it would have been better to wait for the 3.14.1 release, but I just found this image online, and it’s close enough