Job Site In Progress: The Web Development Food Chain

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

Content YOUR SOCIAL NEWORKS ARE FACEBOOKINSTAGRAMTIKTOK MY SOCIAL NETWORK IS GITHUB WE ARE NOT THE SAME

Content BY O toggl Goon SquAD DEVELOPER LIMBO- BEING AWAKE OUTDOoRs aT NoON (WITH NO ACCESS TO A PLAYSTATION) PRObLE AND DOCUMENTATION DOCUMENTATION MARKETING SALES- REALLY SUCKS "YOU'VE ALREADY CODED HALF YOUR SITE? O LESS WORK FOR US, AMIRITE ? " TECHNICAL RECRUITERS - "HEY GIRL, DO YOU KNOW JAVASCRIPT? GLIENTS NEW IDEAS "HANDS-ON " CLIENTS "MINOR CHANGES" THE FIXER' SCOPE CREEP UCTIC MANAGEMENT Now iM JUST ONE TALKING AGOVI IT DONE YE USELESS MeETING BAD cODE TO LOOK AT YOUR OLD CODE LEGACY CODE TERRIBLE SOLUTION HOLDING EVERYTHINZ TOGETHER YOUR GES IDE INTERNAL AD-HI ITERRUPTiONS MESTERDAY MTHICAL PLACE WHERE STUFF HAS TO BE READY YEAH (ACCORDING TONI GE TO INFO FR TOMORROW "ARE YOU DOING ANYTHING?" TACIRCLE HOPELESS PLACI A BROKEN COFFEE MACHINE MART VIRKUS '17 Proarammer-umor.to TOGGL.COM

Behold, the pinnacle of security theater! First, let's expose our database directly through an API endpoint because REST is "too complex." Then, let's sprinkle in some AI validation using GPT to check if SQL queries are safe—because regular expressions and parameterized queries are just so last decade . Nothing says "I'm a 10x developer" quite like importing five different packages, exposing your database credentials in plaintext, and asking an AI if DROP TABLE users; seems fishy. The cherry on top? That 403 error when the AI says no—as if hackers will politely accept rejection and go home. SQL injection protection via AI prompt? Congratulations, you've invented a security vulnerability with a carbon footprint!

Content REALLY, A SENIOR ENGINEER WITH YOUR TALENTS DEVELOPING WITHOUT ME? imaflip.com IT'S PEACEFUL HERE

Content Me: adds how about you suggest some bitches to my code Copilot: well now I am not doing it ProgrammerHumor