The Meeting Cancellation Euphoria

Content Huenry Hueffman HenryHoffman I fucked up Git so bad it turned into Guitar Hero 2 Follow Pathetic. All Branches V Show Remote Branches Ancestor Order Graph

NASA, the literal ROCKET SCIENTISTS who put humans on the moon, fixed a multi-billion dollar space telescope with the EXACT SAME TECHNIQUE I use when my Wi-Fi stops working! 💀 The pinnacle of human engineering and astronomical achievement, the Hubble telescope, gets the same treatment as my $20 router from Best Buy. I'm SCREAMING! All those PhDs and fancy degrees, and their ultimate solution was "have you tried turning it off and on again?" The universal IT support mantra transcends even the vacuum of space!

That moment when your codebase is held together by duct tape and prayers, but you keep adding more tape instead of rebuilding the foundation. The Senior Dev has finally had enough of your if/else spaghetti monster and temporary fixes that somehow lasted 3 years. Every programmer knows the temptation of the quick fix - "I'll just add this one exception case" turns into twenty nested conditionals that nobody understands anymore. Meanwhile, the tech debt grows stronger than Heisenberg's empire. Time to break the cycle and actually fix the architecture... right after this one last workaround.

Content 5220,000 Marketing Manager 3500.000 CEO 120,00 UX Manager 120,000 IT Manager Dave 75,000 Senior Programmer ProdrammerHumor.io CIO Project Manager 140,001 Product Owner 395,000 Business Analyst DODO Product Manager

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

Content No thank you! We don't want any more arithmetic logic units, random access memories, or other higher-level circuits. A B Y And what about primitive logic gates? NANDalf! imaflip.com