We Have A Style (And We'll Tell You About It)

The eternal dance of resume inflation. On your CV, you're architecting "decentralized real-time data flow" systems like some blockchain-wielding wizard. In reality? You're just reading from stdout and piping it to stdin. That's literally Unix 101 from 1971, but slap some buzzwords on it and suddenly you're a distributed systems expert. Every developer knows the game: take your mundane daily tasks and translate them into enterprise-speak that makes HR's eyes light up. "Implemented cross-process communication protocols" sounds way better than "I used a pipe." The swole doge vs regular doge format captures this perfectly—we all present ourselves as architectural gods while internally knowing we're just plumbers connecting pipes. The job market runs on this mutual delusion, and honestly? If HR is gonna filter for keywords instead of skills, might as well give them what they want.

The ultimate irony of programming in one image. The creator of Linux has a minimalist setup with just a single monitor and basic desk, while the guy who couldn't pass intro programming has the full RGB gamer battlestation with three monitors and enough cooling fans to create a small hurricane. It's like showing up to a coding interview in a Ferrari when you can't write a for loop. The tools don't make the craftsman—a truth every senior dev learns after their fifth mechanical keyboard purchase.

Content "Jenkins? In 2024?" "Bitbucket? In 2024? me reading these comments with both jenkins and bitbucket

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 ays since last timezone issue

Content Bogdan Botezatu bbotezatu Happy 25th birthday, Linux! Here's your f-ing cake, go ahead and compile it yourself. BUTTER BUTTER