Order by Memes

What happens when a DBA designs a clock? You get Roman numerals in completely random order because SQL queries without proper constraints do whatever they want. Notice how IX (9) is where 4 should be, and V (5) is at 6 o'clock. The comment "It Will Work This Time" is the eternal lie every developer tells themselves before running untested SQL in production. Spoiler: it never does.

OH. MY. GOD. This is what happens when you let a database admin design a clock! The numbers are in complete chaos because some SQL-obsessed maniac decided to ORDER BY DIGIT NAME DESC instead of, you know, ACTUAL NUMERICAL ORDER like a SANE HUMAN BEING! The SQL query literally sorted the digits by their spelled-out names in descending order, so "twelve" comes before "three" which comes before "ten" and so on. Can you imagine trying to tell time on this monstrosity?! It's like asking what time it is and getting back "SELECT CURRENT_TIME FROM REALITY WHERE SANITY = NULL"!