Github Copilot Is Wild

Content NOOO!! You can't just compare strings as numbers! "b" "a" true "a" "b" false JavaScript: HAHA GO BRR!! TheArmagan

Content The junior dev when the senior dev talks about anything above basic console applications with no libraries like your funny words magic man imgfip.com

Nothing says "I panicked during a coding interview" quite like writing FizzBuzz with three separate if statements and continue in each one. The interviewer's face progression from neutral to facepalm to disbelief is the universal reaction to code that technically works but makes seasoned developers want to throw their mechanical keyboards out the window. Pro tip: If your solution has more continue statements than actual logic, your future teammates are already updating their resumes.

Content Thabiso magwaza 3rd Software Engineer at Discovery Limited 1W Software job postings be like: - Bs Computer science degree, master in machine learning and Al - Competent in C, C, Go, Javascript, Assembly, Linux and SQL - Competent with Docker, Kubernetes, AWS, Azure - Competent in Web Design, back-end design, database design, big data - Must have been to the moon at least once, fought in WW2 and can ride a parashoot - A pilot's licence would be an advantage 6, 9 757 Comments Like E Comment ( Share

Content If you're hiring a front end dev, here's my resume. I can start on Monday. I can center a div.

Your friend just reinvented callback hell, but with extra steps. Instead of using a simple await sleep(1000) or even setTimeout , they decided to create the world's longest promise chain that looks like it's trying to reach the bottom of the Mariana Trench. The beautiful irony here is that promises were literally invented to avoid this kind of nesting nightmare. It's like someone handed them a ladder and they chose to stack chairs instead. Each .then() is probably just wrapping another promise that resolves after a delay, creating this magnificent stairway to callback heaven. Fun fact: This code probably has more indentation levels than the JavaScript spec has pages. The real kicker? A simple utility function like const sleep = ms => new Promise(resolve => setTimeout(resolve, ms)) would've saved them from this horizontal scroll of shame. But hey, at least they're consistent with their suffering!