Great Now We Wait

Content Clement Mihailescu Following Co-Founder CEO, AlgoExpert Ex-Google" 1w G My heart goes out to all backend and infrastructure engineers. While frontend engineers get praised for their beautiful UIs and product managers get credited for their awesome products, backend infra engineers get little to no recognition, except when a service goes down for 5 minutes, at which point they get called garbage engineers who can't keep a service up. We appreciate you, backend infra engineers! softwareengineering programming 23,738 580 comments Love Comment Tell them what you loved" Share Send ProdrammerHumor.io

Content Nader Dabit dabit3 587 Why is the result of ('b''a' 'a' 'a').toLowerCase 'banana'? javascript type-conversion I was practicing some JavaScript when one of my friends came across this JavaScript code: document.write( ('b' 'a' 'a' 'a'). toLowe rCase ()); The above code answers "banana" ! Can anyone explain why?

Content This is Mike Mike's job is to write highly performant code that can work under load and handle lots of requests concurrently. His apps also have to be highly precise and reliable - all user inputs must be thoroughly validated, concurrent requests must not interfere with each other, there must be absolutely no vulnerabilities. Mike needs to know how to find the best compromise between performance and data consistency: when to invalidate the cache, whether or not to wait for database write acknowledgement, and so on. He also needs to assume that his code will run in a cloud environment, in volatile containers that can be destroyed at any time. Mike is a backend developer. This is Jane Jane's job is to write apps that will run on 200 different versions of 10 different platforms, on thousands of different devices with various screen sizes. All these devices must be able to download, parse and bootstrap Jane's code in under 200 milliseconds. Jane works with a complex state tree that can be modified by various kinds of events, and the app's UI must be instantly updated to reflect these changes in the most efficient manner possible. Jane needs to know how to do code splitting, responsive layout, render virtualization, serverside rendering, handle browser-specific quirks, and so on. Jane is a frontend developer. This is Bob Bob thinks that Mike is a real developer, but Jane isn't. Bob is a moron.

Content 4:11 Software Developer (Entry-Level) DPS Telecom 4955 E Yale Ave, Fresno, CA 93727 Job details Salary Up to 18 an hour Job Type Full-time Qualifications Software development: 1 year (Preferred) Benefits Pulled from the full job description 401(k) 401(k) matching Health insurance Life insurance Dental insurance Paid time off Show 2 more benefits Full Job Description Write software code for embedded devices that protect lives during emergencies. Using C and Javascript, you'll write bug-free code to power remote monitoring systems nationwide. th Apply now You can advance very quickly if you develop strong skills indeed.com

Junior dev really said "let me commit every security vulnerability known to mankind in a single PR." We've got hardcoded API keys, passwords, AWS secrets, database URLs with credentials, and a fetch request to "malicious-site.com" that literally steals the keys. There's even an eval() thrown in there for good measure, because why not execute arbitrary code while you're at it? The cherry on top? Line 57 sends all your secrets to a malicious site with a query param called "stealkey". Subtle. And let's not ignore the loop creating 10,000 arrays or the invalid JSON parsing attempt. This isn't just bad code—it's a security audit's final boss. The senior dev reviewing this PR is having an existential crisis. Do you reject it? Do you schedule a meeting? Do you just... quit? Sometimes the best code review comment is just a long, contemplative sigh.

When the senior dev asks you to explain your code to a non-technical stakeholder, and suddenly you realize you don't actually understand what you built either. That moment when your elaborate JavaScript framework is just a glorified rubber duck – it looks impressive floating in the bath of your codebase, but you have no idea what it's actually supposed to do. The perfect representation of every technical interview where you confidently wrote something that worked by accident.