Code Hoarding

When your security audit consists of pressing "OK" and moving on. Somewhere, a security engineer just felt a disturbance in the force. The perfect mix of horrifying vulnerability and casual acknowledgment - just click "OK" and pretend you didn't see that any user could inject JavaScript and rewrite an entire website for years. Security through obscurity at its finest.

Content Stephen Gower As someone who has been developing websites since NCSA Mosaic was the only browser available, I'd just like to say that I'm really fcking tired of all the smart assholes out there continuously developing entirely new ways to build web applications. It started simple enough, just html and javascript. Then Cold Fusion. Then java applets. Then java servlets. Then 5 or 6 different Java application servers, EJBs, JSP, struts, XSLT, PHP. But screw all of that. We need Spring. No wait, we need Ruby.and Rails. Wait, we need Query. screw Query. We need AngularJs, and Backbone, and Ember! The world just won't be right until we have 12 different ways to do the same thing in Javascript! Forget all those server-side things you learned. Node js is here! No-wait. F'ck Node. Use Google Go! Honestly how many times are we going to re-invent this wheel? Unless you stay current with all of this nonsense, you basically become unhireable. I'm sure some of you 20 and 30-somethings have already experienced some of this fatigue. Now just imaging 10-15 more years where every 3 years a good portion of what you learned before is now obsolete, and you'll feel like I do.

Content IT'S A Frontend IT'S A Backend JS Program HANNAHHILLAM FEB 7 201 15 IT.. ? T'S BOTH. HATE IT

Content Requirements: Minimum of 710 years of experience in .NET backend development Experience working with RESTful APIs, JSON, and XML Excellent understanding of software design patterns, architecture, and clean code principles Proficiency in Jira Excellent command of the English language

Paying $1200/month to use GPT-4 to uppercase text. That's like hiring a brain surgeon to put on a band-aid. The real kicker? Someone spent their entire weekend auditing API costs only to discover they could've just used .toUpperCase() and saved $1000. The most expensive string transformation in history. Somewhere, a regex is laughing at us all.

Ah, the classic developer passive-aggressive error message. Instead of just saying "endpoint not found" like a normal person, this dev decided to write a whole novel about the user's life choices. The highlighted code shows what happens when a 404 error occurs during a password reset - rather than blaming the system, the developer crafted an elaborate user backstory involving forgetfulness, remembering, logging in, account deletion, and then clicking a stale link. That sarcastic "Wow! What a journey!" at the end is the digital equivalent of a slow clap. I bet this dev also names variables after their exes.