This Is Fine: When Code Burns And AI Can't Save You

When your colleague asks about your Pull Request and you casually mention you were "vibe coding" while the stats show +93 lines added, -38,918 lines deleted. That's not coding to a vibe—that's coding during an existential crisis. Nothing says "I'm totally fine" like obliterating 38K lines of code on a Tuesday afternoon. Management will definitely not notice this minor refactoring.

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 HOW TO DEBUG YOUR CODE Start Is there a (bug? Yes You're lying. - Do you know the problem? No Try something random. Yes 7 Fix it. Did it work? No Yes Did it create more bugs? Try and break something. No. Are you tired of debugging? No Yes Yes Your code is still buggy.

Content Twiteeyapa twiteeyapa 1 had a problem, I decided to write a program to solve that. Now I have 1 problem, 9 errors and 12 warnings.

The tech community's version of natural selection: watching newbies confidently throw around terms like "bricked" without realizing they're essentially announcing "I permanently destroyed my device" rather than "it's temporarily not working." Nothing quite like the silent judgment of seasoned engineers watching someone declare they've "bricked" their laptop because the battery died.

Content Using pointers in C be like: Oh... you want a star? EVERYTHING BROKE WE ARE ALL GONNA DIE (ab - 1) Dib(ab - 1 1) x2 7X) x(x -y) 2 6 x2 Maybe two stars? Ah okay, that works! ProarammerHumor.io