https://www.thewindowsclub.com/how-to-disable-windows-thumbs-db-files-from-being-created this kills that.

.Trash-999 was already taken by a metal band.

Metadata that’s a holdover from the 1980s MacOS behavior. Hilariously, today, NTFS supports that metadata better than Apple’s own filesystems of today. They can hide it in Alternate Data Streams.

defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool TRUE

Helps a bit.

It helps to be a little bit stubborn, but mostly, remind yourself it’s just software at the end of the day too. So many devs are judgy and think there is only one “good” way to solve a problem, which ends up creating a sort of tunnel vision. As soon as you let that go and just know that every problem could have any solution, especially the unexpected, you see your way through faster.

It doesn’t matter if the way it was working is “right” or not, it was working, for reasons, so fixing it, is just teasing out those reasons. Be it from humans that may still be around, but most of the time, by feeling the code out.

I even see the struggle externally from afar when companies I used to work at release a new feature that touches very legacy code and, time and again, the new feature is buggy AF. The new dev likely had no idea what the old dev was thinking or why, and thusly, breakage. Neither of them is right or wrong, the solution from the past likely was obscure due to constraints that no longer exist, the new solution can be done easier due to a plethora of libraries that now exist, and getting newEasy to jive with oldBespoke trips the new dev up as they unravel what looks like pure chaos.

Works so well, and soothes the warning annoyance brain, and keeps warnings from eventually becoming errors.

It’s rare to see a newborn meme. Soon it will be pixelified to all the doom.

…this hurts my brain. That being said, I’d probably also try it for the lulz, but I’d never bother support about it, because I knew what I was doing was insane.

Oh, apologies for my suggestion before seeing this comment hahaha!

CAN devices I have limited experience with, but I know at least in the automotive industry, vehicles often have various CAN devices that have various sleep states. Like, shut car off, it holds brake system for a few minutes and then unlocks the brakes and that ECU shuts down. Later on, an emissions ECU may run a self-diagnostic. After a few days being powered off, the security ECU goes into low power and turns off wireless doorlocks. After the voltage drops too low, the ECU in the head unit ostensibly shuts down, and the next time the car is started, the head unit has to do a cold-reboot and takes a fortnight.

Could be one of those CAN devices takes some time to get into the “off-adjacent” state to manifest the bug?

Could the time delay in being able to reproduce relate to some piece of code that has a timeout (thinking login timeout, cookie expiration, auth timeout, that sort of thing.) Or likewise, if the computer in question has multiple shutdown phases, like how many computers today “sleep” to RAM, and then an hour later sleep to disk in a more hibernatey fashion and fully power off? (Or some weirdness like how Windows shutdown now is ostensibly a hibernate, but a reboot is actually a full “power down power up” without shutting off power.)

I like @Buddahriffic@lemmy.world 's take on being wall-clock-based. I once had a bug with some software that would just go belly-up on certain days for no reason whatsoever in a datacenter 2000 miles away. After having worked on some bare metal servers in the past and learned all about thermal issues firsthand, I checked the weather in that region. It only seemed to happen on extremely hot summer days, at the day’s temperature peak. Turns out the datacenter vendor had a cooling problem in that section of the DC and they were unaware of it…

Crazy sometimes how bugs manifest.

There’s a weird obscure bug in M$ Remote Desktop in Windows 11 Pro I spent entirely too much time trying to track down, as a user. (Yes, the first mistake was ever getting near Windows, but anyway.)

It looks like there is some kind of counter that now exists in number of logged in sessions, and each RDP session counts as a one-time-use session. The local user does too.

• If you log in locally on first boot, there’s a 25% chance you’ll be able to log in remotely from one machine once or twice.
• If you log in as a remote user from boot, you’re more free to log in remotely, possibly from two different machines about 75% of the time, but if you just use one other machine, pretty much forever.
• Rebooting always solves the login issues, so much so that a terrible terrible workaround was employed. Enable OpenSSH server (now included in Windows) on Windows, to SSH into the box (which, reliably works every time no matter what) and reboot it.
• So many Internets on the topics, including using their old RDP driver, that the new driver may be cranky, that the host graphics drivers may have an impact, that the BIOS OOB management may have an effect. Nothing ever fixed it consistently.

Thankfully, my life means too much to me to go further down the rabbit hole and I don’t have to use Windows as much anymore, and hopefully soon never, but…its like they took a whole team of engineers to break something that has worked amazing since the early aughts and just firehosed pigeon turds all over it.

They obviously care enough to keep it working as they renamed the RDP app to “Windows App” in the last year, but don’t care enough to make it work correctly?

Yeah, it just makes you annoyed, especially when having worked on (some product) and it is years later and you are like, “we fixed this 10 years ago, you morons, how did you let this regress?”

Now if only Docker could solve the “hey I’m caching a layer that I think didn’t change” (Narrator: it did) problem, that even setting the “don’t fucking cache” flag doesn’t always work. So many debug issues come up when devs don’t realize this and they’re like, “but I changed the file, and the change doesn’t work!”

docker system prune -a and beat that SSD into submission until it dies, alas.

Also, if you develop on a Mac, slow disk sync on their modern OSes not picking up the change. Or if you use Docker, it caching a layer that it shouldn’t. The future has weird new problems sometimes.

I didn’t know why a person would go to these lengths to deal with a misbehaving computer, as compute devices are generally for work, and need to work in order to do work, and any kind of crash is going to get my entire focus until it is banished to Hades…

…but then, learned something along the way I probably otherwise would not have, because of @bleistift2@sopuli.xyz’s tenacity.

Using modern tech with its associated crappy software lifecycle to save cost is a heavy gamble, however. Instead of breaking Reddit for a couple of hours, they can’t fire their RCS thrusters to avoid collision with space junk because some stupid NPE that was missed in the QA process that no longer exists because that team was replaced with AI.

LLMs are really fucking bad at math. They’re trying to find the statistical close answer, not doing computation. It’s rather mind-numbingly dumb.

And a new set of dependency problems depending on the base image. And then fighting layers both to optimize size, and with some image hubs, “why won’t it upload that one file change? It’s a different file now! The hashes can’t possibly be the same!” And having to find hackey ways to slap it so the correct files are in the correct places.

Then manipulating multi-arch manifests to work reliably for other devs in a cross-processor environment so they don’t have to know how the sausage works…

Honestly surprised they still underpay versus the industry standard. And still overwork to death. They’re so profitable, they could drop all that behavior. They’re a cult that has to legally allow people to leave or they’d probably just enslave them. Can’t even use their products anymore, knowing that.

You think Thunderbird is insulated? Their latest big drunk UI lift seems to have somehow made it even less intuitive.