Improper Error Handling Be Like

Content Asking a software developer to come and fix your hardware problem is like asking Leonardo Dicaprio to come and fix your TV. ProarammerHumor.io

Content Ricky rickhanloni We don't need everyone to upgrade log4j, just enough for herd immunity to takeover 6:55 PM Dec 12, 2021 Twitter for iPhone 1,025 Retweets 107 Quote Tweets 5,119 Likes Ricky rickhanlonii Dec 12 Replying to rickhanlonii my repo my choice 3 tV 41 554 the squirrel in the tree ay A ( Dec 12 Replying to rickhanlonii do you really even know what's in those patches? could be worse than the actual vuln 9 4 17 21 377 ars Patch fixing critical Log4J 0-day has its own vulnerability that's under exploit If you've patched using Log4J 2.15.0, it's time to update again. Stat! by Dan Goodin - Dec 16, 2021 8:40am AEDT r Login to bookmark 10 Wikimedia CommonsAlex E. Promos Last Thursday, the world learned of an in-the-wild exploitation of a critical code-execution zero-day in Log4J, a logging utility used by just about every cloud service and enterprise network on the planet. Open- source developers quickly released an update that patched the flaw and urged all users to install it immediately. Now, researchers are reporting that there are at least two vulnerabilities in the patch, released as Log4J 2.15.0, and that attackers are actively exploiting one or both of them against real-world targets who have already applied the update. The researchers are urging

Content (DEV The Practical Dev thepracticaldev The feature where Atom slows down and crashes if I open a big file really helps me keep my code concise and my classes small 21:44 PM - 09 Mar 2017 9 17 409 1152

Imagine inheriting a dumpster fire of AI-generated spaghetti code, and someone thinks you can fix everything from authentication to CI/CD with the budget that wouldn't even cover your therapy sessions after seeing the codebase. That $2,500 budget is the real joke here. That's not even enough for the coffee you'll need to stay awake while deciphering what the hell the AI was thinking when it generated this monstrosity. This is the modern tech equivalent of "I need you to rebuild the Titanic using only duct tape and a tight deadline. Oh, and can you make it unsinkable this time?"

I see we've discovered the elusive "filterception" in the wild. Some brilliant mind decided to filter the filters with a filter that filters filters. And they even helpfully commented "// filter" at the end – you know, in case the five other instances of "filter" weren't clear enough. This is the coding equivalent of saying "Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo" and expecting it to make sense. Somewhere, a code reviewer is staring at their screen, questioning their career choices.

That Instagram vs Reality moment in software development. Left side: The "vibe coders" pointing guns at their own feet with their "I know enough to be dangerous" attitude. Right side: Actual coders aiming with precision after years of debugging catastrophes caused by the first group. Nothing says "experienced developer" like knowing exactly where to point blame when the production server catches fire at 2AM.