And Chatgpt

The quintessential developer evolution captured in one perfect meme! Junior devs frantically try to memorize what every line of their code actually does, while senior devs have transcended to a higher plane of existence where they just... don't. After years of typing git commit -m "fix stuff" and console.log('why god why') , you eventually reach the zen-like state where your fingers write code your brain doesn't even fully comprehend anymore. The code works? Ship it! Documentation? That's what comments were invented for (that you'll never actually write).

The eternal developer struggle captured in its purest form. You're drowning in buggy code while desperately pushing against the current with help from the holy trinity of survival: StackOverflow answers, random blog posts from the dawn of Web 2.0, and occasionally divine intervention. Meanwhile, your code is like that van – somehow still functioning despite being submerged in technical debt. The best part? We've all been that dog, just watching the chaos unfold while silently wondering how we got ourselves into this mess in the first place.

Content Friend: Hey you're like an engineer right? Me: Yeah software engineer. Friend: Great, there's something wrong with my refrigerator can you fix it? Me: ??? ??

The eternal struggle of learning Rust in a nutshell. One week into Rust programming and you're already being interrogated by the borrow checker - this adorable orange crab (Ferris, the Rust mascot) hitting you with conditional logic that makes perfect sense to the compiler but breaks your brain. "If not friend, then why friend shaped?" is basically what your code says to the compiler when it refuses to compile despite looking perfectly valid to your sleep-deprived eyes. The borrow checker is simultaneously your strictest teacher and your most confusing nemesis.

The face of pure, unadulterated doubt . Every developer knows that look—it's the one you make when your colleague swears their 5-year-old Stack Overflow solution will fix everything. The same expression you had when the junior dev said "I rewrote it in Rust over the weekend" or when management promised "just one more small feature before release." That suspicious squint is the universal BS detector that evolves after your 50th "final version" turns into version 17.3.2-hotfix-please-god-work.

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