Stupid as hell fact :
Some 2nd graders (9yrs old) in Korea use VI to do coding in hagwons.

(See here : https://translate.google.com/transl... - translate from Korean)

I wrote a whole article about it, and oh wow, it still exists. It was probably the first optimization I ever did in my life, and it was while I was learning SQL.

And writing an edu-tainment article aimed at total laymen as well as beginners was also fun.

http://swczdev.blogspot.com/2010/...

Sadly, czech language only. But... the english autotranslation actually looks readable:
https://translate.google.com/transl...

Long story short, though: 4 or 5-table join going from 7 seconds before optimization, to 0.08 seconds after optimization. Both were written by me, the optimized one was written without any reading on how to optimize SQL, based purely on me actually stopping to think about how I can reduce the DB load based on the little that I knew about how SQL servers work.

Optimization made it about 99,9999422% more efficient, based on my improvised efficiency metric of how many rows the query retrieves and produces versus how many are thrown away on the end due to the WHERE part of the query.

And that was also the day when my question of "what is there even to optimize in SQL?) was answered... by myself.

"We'll publish critical vulnerabilities in PGP/GPG and S/MIME email encryption on 2018-05-15 07:00 UTC. They might reveal the plaintext of encrypted emails, including encrypted emails sent in the past. #efail 1/4"
https://twitter.com/seecurity/...

Let's see how this unfolds. While there is chaos I trink some tea and laugh, because I never send critical information over e-mail. 🧐🍵

https://m.facebook.com/story.php/...

WATCH NOW THANK LATER. (It’s rubber duck related)

Sorry about the Facebook video