Frontend vs Backend: The Sock Edition

Content Debug: 2 pytest for test scheduler. TestScheduler.test execu... Debugger console AZ IF Terminated testscheduler TestScheduler O test execute jobonce 96 B Tests passed: 0 of 1 test Fatal Python error: Segmentation fault Thread 0x00007d934d96640 (most recent call first): File "usrLibpython3.10threading.py", line 324 in wait File "usLibpython3.10threading.py", line 607 in wait File " homeeonraider. localshareJetBrainsToolboxappsPyCharm-Pch-0223.8617. File " homeeonraider. localshareJetBrainsToolboxappsPyCharm-Pch-0223.8617. 219 in run File "usLibpython3.10threading.Dy", line 1016 in bootstrapinner File "usrLibpython3.10threading.py", line 973 in bootstrap

Content LETS TALK ABOUT THE CODE OF YOURS. I THINK ITS GOOD EXCEPT IT SUCKS. SO LET ME DO IT MY WAY, AND THAT WAY IT MIGHT BE REALLY GOOD

Content lEs Untitled - Paint View cut En Copy Paste Select Crop L Resize Rotate made 200 300 INODOZA F Outline Brushes Tanie Shapes 400 500 600 700 Color Golor 800 Edit Colors 900 1000 1100 UX UI graphic designers We needyou? please apply ig 19 1400 x 953px 100

Content listless Is.!! An error occurred attempting to read properties for the "Burger Sidetext resource Ape. Invalid Class String Eror Id -2147221005(8004018)

This meme perfectly captures the existential crisis of being a software engineer. Your boss thinks you're just sipping coffee all day (clearly they've never seen your 3 AM debugging sessions). Your friends imagine you're living the dream with gaming and foosball breaks (ha, if only). Mom still thinks you're some kind of computer repair wizard (bless her heart). But the reality? You're just a pasta chef, frantically trying to untangle spaghetti code that someone else wrote five years ago with zero documentation. The irony of calling yourself an "engineer" while spending 90% of your time wondering why adding a semicolon fixed everything is just *chef's kiss*. The pasta metaphor is painfully accurate - both require hours of preparation, both get messy quickly, and both leave you questioning your life choices at 2 AM.

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