Have You Tried Turning It Off And On Again

Ah yes, the sacred ritual of writing tests. Nobody wants to do them, but when that rare moment of inspiration strikes, you spend 45 minutes crafting the perfect variable name instead of actually testing anything. Look at those beautifully named constants! jennyWithCountryCode and jennySansCountryCode - probably took longer to name than the actual function they're testing. And you just know that developer felt an inappropriate amount of satisfaction after typing them. The real unit test was the clever variable names we made along the way.

The ultimate programmer betrayal—your brain waits until you're horizontal to unleash its genius. Eight hours of staring at the screen? Nothing. The second your head hits the pillow? BAM! Your subconscious pulls the solution from some neural filing cabinet it's been hiding all day. That smug little brain even has the audacity to mock you for not seeing the obvious fix sooner. Meanwhile you're lying there at 3 AM contemplating whether to get up and code or pray you'll remember it tomorrow. Ten years in the industry and I'm still having midnight standups with my cerebrum. The real sprint planning happens between REM cycles.

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 Company: our projects are well structured so errors are easy to find. Their projects: Languages Makefile 18.7 C 11.9 Rust 9.3 C 14.3 C 10.8 Java 9.3 Other 25.7

Developers spend hours designing "intuitive" interfaces, convinced that no user could possibly misunderstand them. Then reality strikes with the subtlety of a truck carrying lumber sideways. Users will find ways to break your system that you couldn't imagine in your worst fever dream. This is why we have error messages like "Please don't hold your phone upside down while shaking it violently and trying to log in." Murphy's Law of UI: if there's a wrong way to use it, someone will find it... and then file a support ticket.