Satan Will Also Be Scared

BEHOLD! The most exquisite example of "it's not a bug, it's a feature" I've ever witnessed in my ENTIRE LIFE! 😂 This magnificent function claims to validate emails but actually does NOTHING of the sort! If it can't validate? Just assume it's valid! If the filter function doesn't exist? VALID! The ultimate "this is fine" meme in code form. Somewhere, a security expert is having heart palpitations while a project manager is celebrating how quickly this ticket was closed. Pure. Evil. Genius.

Content Druide tigarsdruide japanese chefs: you have dutifully made nothing but tamagoyaki for the past 6 years. I deem you now worthy to learn the advanced art of putting fish into a tube web devs : vou just finished bootcamp? great. here's 15 million SSNs

Content Joanna Stern JoannaStern Since the iPhone 14 went on sale, the 911 dispatch center near Kings Island amusement park has received at least six phones calls saying: "The owner of this iPhone was in a severe car crash.. Except, the owner was just on a roller coaster.

Content Code compiles: No errors Code runs: No results

Content I've interviewed a lot of people over the last year (Java), and my favorite test is to throw a Stack Trace at them and ask them to figure out what the problem is. The answer is actually quite clear, however. Half of them don't know it's called a stack trace. Some don't know what they're looking at (BYE!). Several focus on the wrong section of proprietary code. Some ask to "open a debugger". however the answer is right there in plain english if you just read the method names. Many don't realize the line numbers are RIGHT THERE, and then start focusing on the lines ending with "Compiled Code". Then there are the ones who work their way up from the bottom, starting with the application container code, and lose their minds. Some who figure out what is happening don't have a solution to prevent it from happening. No, I'm not sharing the trace; suffice to say it's been reviewed by more than 5 of my peers and they all passed. Like Reply 1h Edited I mean, it isn't hard to eliminate people with a coding question. Do you find it impossible to teach people how to read text stack traces, or is this a skill without which they will be unable to do anything of use, or do you just not want to hire anyone? 1 am serious. 1 can come up with dozens of useful programming skills I can test a candidate on that most perfectly skilled programmers would fail. Start with eliminating people who can't code at all. Then find out what they can do that could be useful. If I have 5 people who can already take a printed out stack crash dump, I probably don't need another, and if I do, a qualified candidate can be taught that skill by someone who knows it in under a week. Then again, maybe you work for Stack Trace Inc, and your entire job is looking at stack traces. If so, by bad. Like Reply 22m

The horrified expression of the Senior Developer looking at the Junior Dev's code is priceless! That moment when you ask what's in their codebase and they casually reply "A smoothie" while sitting next to a monstrosity of deeply nested if statements is peak software engineering trauma. It's like opening someone's function and finding a 12-level deep conditional hell where each branch leads to another dimension of logic spaghetti. The Junior Dev has no idea they've created an eldritch horror that will summon the debugging gods at 2AM during production. Meanwhile, the ostrich perfectly represents the code review process - just stick your head in the sand and pretend you didn't see those 17 nested conditionals that could be replaced with a simple switch statement!