Here’s my resignation.

Either it’s your fault, it’s going to be your fault, or you’re cleaning this up. Bottom line: there’s a damn-near lethal amount of incompetence in the building and it’s time to part ways.

Way ahead of you: they can’t even see my car from the house. This way, it’s possible to vanish long before anyone figures it out.

Protip: do this but do NOT bring a whiskey flask or edibles. Yeah, it may take the edge off, but you may need your wits about you.

This is the mid-to-final stage in the family trauma galaxy-brain meme:

1. I’m screwed up, and it’s my fault
2. I’m screwed up and it’s my family’s fault
3. My family screwed me up because they’re also screwed up
4. My family screwed itself up, from long before I was born
5. If I stick around, I’m gonna get more screwed up

Also, if you look around and think about it, you may be able to identify which family members are practicing limited/no contact. They may be screwed up too, but at least they’re aware of it.

could you imagine splicing stuff like this?

Ugh. Honestly, I’d quit. And I actually like repairing things. You’d have to bring in “the guy” that just really enjoys this kind of repetitive and error-prone repair task.

Context: https://www.reddit.com/r/cablefail/comments/5novv2/3900_pair_underground_splice_that_got_wet_due_to/

No, I get you. The artifacts for these you see at museums are impressive. The bigger ones would make some great bookends.

If this is how the Western world arrives at harm reduction and UBI for everyone - that it’s just good business - I’m not even gonna be mad.

Java itself is kind of blissful in how restricted and straightforward it is.

Java programs, however, tend to be very large and sprawling code-bases built on even bigger mountains of shared libraries. This is a product of the language’s simplicity, the design decisions present in the standard library, and how the Java community chooses to solve problems as a group (e.g. “dependency injection”). This presents a big learning challenge to people encountering Java projects on the job: there’s a huge amount of stuff to take in. Were Java a spoken language it would be as if everyone talked in a highly formal and elaborate prose all the time.

People tend to conflate these two learning tasks (language vs practice), lumping it all together as “Java is complicated.”

$0.02: Java is the only technology stack where I have encountered a logging plugin designed to filter out common libraries in stack traces. The call depth on J2EE architecture is so incredibly deep at times, this is almost essential to make sense of errors in any reasonable amount of time. JavaScript, Python, PHP, Go, Rust, ASP, C++, C#, every other language and framework I have used professionally has had a much shallower call stack by comparison. IMO, this is a direct consequence of the sheer volume of code present in professional Java solutions, and the complexity that Java engineers must learn to handle.

Some articles showing the knock-on effects of this phenomenon:

• https://stackoverflow.com/questions/11865307/how-to-expand-size-of-java-stack-trace-to-see-bottom-of-stack-triggering-a-sta
• https://www.reddit.com/r/java/comments/16g30jx/can_java_errors_stack_traces_be_longer/
• https://www.quora.com/Why-does-the-Java-Spring-Framework-produce-gigantic-unreadable-stack-traces
• https://community.splunk.com/t5/Splunk-Dev/What-are-the-best-extraction-methods-for-Java-Stacktrace-Errors/m-p/380397
• https://stackoverflow.com/questions/65436457/springboot-stack-trace-logging-filter-only-from-my-packages

Yes, but “Proto Indo-European” doesn’t exactly roll off the tongue. /s

I feel like this is just a lower-stakes version of “RedBull & vodka.” If that’s true, @The_Picard_Maneuver@lemmy.world, then this is a recipe for a bad hangover.

Good point.

Calling in sick:

Calling in, sick:

Oh no, I have to press up 200+ times if we’re counting all the detritus and failure in my command history.

There is an advantage to this approach though: fewer errors. You’re plucking a known working command from a list instead of manually typing a (possibly) broken version of it. Worse yet is when it’s a command where typematic mistakes cause unintended side effects like data loss. So, mashing up 100 times can be pretty smart, especially if you’re not a great typist.

Upvoted for the dancing and singing emoticon. Nice art.

I actually tried to use marketplace a few weeks ago. It was an unmitigated disaster. People either didn’t respond, had stale posts for items, or couldn’t get their act together to have a conversation (even with 12 hours between messages) about how to get shit out of their house. I have never yearned for old-fashioned yard sales so much.

I think a high polling rate matters more with N-key rollover (lots of successive keypress messages in one bunch), which in turn matters for some gaming scenarios.

Model-M from 1992 checking in, with all its PS/2 to USB adapter glory. Works great, and is heavy enough for home defense, removing unwanted fingerprints from walls, and smashing produce.

Are PS/2 ports still operating on hardware interrupts these days? I would expect these to be emulated as USB devices at this point, depending on whatever I/O chipset is in play.

The bit about USB asking the CPU is kinda true? My understanding is that it’s a packet protocol of sorts, so it’s really just writing post-it notes for each button press and leaves them on the CPU’s whiteboard for later.

I agree, but I feel like having the toaster itself catch fire could have been mitigated somehow.

I’m actually kind of amazed that the failure mode for “toaster used sideways” is that it just catches fire. That’s one hell of a design flaw.