I Love Monoliths Also This Is Not Satire

Content FBI FBI Google How to re-attach a detached head Google Search I'm Feeting Lucky Google How to re-attach a detached head Git Google Search I'm Foeting Lucky

Content The world, if Java installer could set Java Home automatically

Content Safari tries to fill username 25 Open ) quarterdeck opened this issue yesterday 8 comments quarterdeck commented yesterday What do you want to do? krisquarterdeck.co.uk From this website Other Usernames... 1 Course in Up Next quarterdeck commented 6 hours ago edited Author Upon further investigation this seems like an absolutely crazy Safari bug and I'm not sure if it can be worked around or not. I noticed that this was only happening on one page of our app. So I systematically commented out each section of HTML to see if any block was affecting it and I found one! 1 narrowed it down to a single p tag which contained the text "Welcome back,". I thought the comma might be causing an issue (no idea why) so I removed it. No change. I thought the word "back" might be making Safari think this was a login page for some reason? So I removed it and it fixed the issue! Crazy. Out of curiosity I tried removing "Welcome" and adding "back" back in. Still didn't re-occur. ?! So it seems only the combination of words "welcome back" causes this to happen. Absolutely no idea why. To confirm I chose another page randomly and put the phrase "welcome back" in a random position on the page and low and behold it caused this to happen again. For some reason the presence of these words on the page is adding the following to the Shadow DOM of the input field: div pseudo"-webkit-credentials-auto-fill-button" role "button" aria-label"password AutoFill" style-"display: Easily the most bizarre bug I've ever come across. 34 106 39 177

You spent days optimizing that SQL query to absolute perfection. Indexes tweaked. JOINs restructured. Subqueries eliminated. You turned a 30-second nightmare into a 0.3-second dream. Your boss was impressed... for approximately 5 minutes. Now they're casually dropping phrases like "real-time dashboards" and "instant analytics" in meetings as if your database isn't already sweating bullets just handling the current load. They have no idea that "real-time" means your beautiful query needs to run every 2 seconds instead of once an hour. Congratulations, you've optimized yourself into a corner. Your reward for fixing the performance issue? A completely unreasonable new requirement that makes the original problem look trivial. The database gods are laughing at you right now.

HONEY, HOLD MY COFFEE! The absolute AUDACITY of returning a 200 OK status while simultaneously screaming "an error occurred" in the response body! 💀 It's like telling someone "Your application is PERFECT!" while secretly setting their server on fire. At least the 500 error has the decency to admit it's having a breakdown, and the 400 acknowledges you messed up. But this? This is pure CHAOS wrapped in a SUCCESS wrapper! Whoever designed this API deserves a special place in developer hell where all their Git commits mysteriously disappear and their IDE randomly changes to Comic Sans.

Content Kat Maddox ctrIshifti 3h tech has three jokes: stackoverflow is mean, javascript is bad, and dark mode is good. my life's goal is to discover a fourth joke 975 1773 669 Kat Maddox ctrIshifti 13m my apologies, quitting vim is the fourth joke. As all 4 tech jokes have now been discovered, I will be closing this account. Goodbye 172 M87