• 0 Posts
  • 117 Comments
Joined 2 months ago
cake
Cake day: January 20th, 2025

help-circle




  • where a crowd gathered for a completely unrelated purpose gets to see the last thing an afghan child at a wedding sees

    I know this probably makes it worse, but the Afghan child most likely wouldn’t even have a chance to see the plane (or more likely, predator drone) that fired the missile that killed them.

    It’s one of the many reasons these children are fucking terrified of clear skies and sunny days.


  • That’s what I do at work, even though I’m salary.

    Management decided to hire a new guy and then have a round of layoffs within 6 months, effectively canning someone to replace him. Since then, we’ve had multiple times where we have hundreds of tickets sitting unassigned because there’s more work than people. So shit sits and falls through the cracks until someone has time or something is on fire.

    It fucking sucks, but eventually the bean counters will see that we actually needed that extra body…


  • It all depends on how time tracking is implemented.

    Tell me I have to account for my time in 15-30 min increments? Fine, I can put it into a spreadsheet and track it.

    Tell me I have to track real time spent? Get entirely fucked, and I hope you’re ok with spending time fixing my time punches because I absolutely am going to forget to open or close a time entry because I’m working on 3-4 tasks at any given time.

    I’ve done both, and while I won’t intentionally sabotage the latter, my rampant ADHD and terrible memory have got my back on that one.



  • Maybe there’s more implementation nuance here but it seems like an opinionated rule that has zero effect on performance unless that code is being called thousands of times every second

    It’s good practice to get in the habit of coding to only do the things you want/need to do rather than hoping the compiler does it for you.

    This particular constructor call may be light, but there may be constructors that have a lot of overhead. Or you might be running alongside 1000 other processes who said the same thing and you start to see performance degradation.









  • Do you remember what you fixed when you fixed it on the window side? Asking because what you’re describing almost sounds like you have a bad driver, which would explain why your Linux side would also have a similar problem, IE locking up completely auddenly, if it had the same bad driver and interacted with the hardware the same way causing a similar crash.

    Honestly, if it’s fixable in the windows it’s definitely fixable Linux. It just might take a little bit more extra work to figure it out.