SQL Time Is Always Wrong Time

Future bedtime stories will feature tales of the mythical AWS outage of 2025. Dad sits there, thousand-yard stare, remembering how he just watched the status page turn red while half the internet collapsed because someone decided DynamoDB should be the single point of failure for... everything. The real heroes were the on-call engineers who had to explain to executives why their million-dollar systems were defeated by a database hiccup. Meanwhile, the rest of us just refreshed Twitter until that went down too.

Content When your code stopped working during an interview Dude you are embarrassing me in front of the wizards.

When your validation logic is too aggressive. Tony Hawk gets deleted because "that can't be the real Tony Hawk" and Dallas Tester gets nuked because an airline's regex thinks he's a test account. Classic case of overzealous input sanitization that treats legitimate edge cases as security threats. This is why we can't have nice names in production. Somewhere, a developer is adding if(name != "Tony Hawk" && !name.includes("test")) to their validation code and calling it a day.

Content Hashing and salting password with BCRYPT Hashing passwords with MD5 and no salt Plaintext password in database Check login S('login") .submit(function (e) e.preventDefault(); if ( ('username).val() 'admin' S('pw').val() "SecretPN1234 ) window.location "admin": else alert('Wrong password"); Passwords

Content 21:54 all 31 Tweet Manuel Frigerio manuelfrigerio Please don't apply for a Senior dev position if your Github looks like this. Tweet bersetzen 1 contribution in the last year FADEMA Less. OBE More 11:05 24.02.23 4,3M Mal angezeigt 619 Gefllt mir"-Angaben 50 Retweets 1.222 Mal zitiert 17 ProarammerHumor io

Content Dakshin K 5:05 PM Query was taking 30 seconds I went and optimised it 5:05 PM and it is now taking? Dakshin K 5:05 PM 45 seconds N 5:05 PM what the