Fucking pieces of shit, if I would have a list of developers that add "Whoopsie daisy, tinky winky compiling stuffie" as error messages, installer steps or as a checkbox in their github issues, I'd break their fucking back and keep them alive, just to ram fucking burning nails into their eyelids and then blast just enough power through them to make them burn and evaporate alive.

2 weeks ago I was writing an `rm -rf --no-preserve-root /` oneliner as a joke - as an answer to a question "I have access to my competitor's server; what should I do?". I was crafting it so that it'd do as much damage to the business (not the server) as it could.

And I accidentally executed it on my work laptop. In the background (with an `&`).

It ran for a good 5-7 seconds on an i7-11850H with an SSD, until I issued a `kill %%`

Good thing it ran as a non-root user. Bad thing - I have no idea what it may have deleted nor whether it touched my /home.

I'm afraid to restart my laptop now :)

whoopsie :)

Whoopsie!

Lead: I want you to make this library we wrote mockable, so that we can write better tests.
Coworker: Ok

...

Lead at the end of the day: How's it going with the library?
CO: Good, I have made all calls to the library mockable.
Lead: you mean inside the library, right?
CO: No, all calls to the library

Lead:

When file managers copy and delete files within the same partition instead of moving or renaming them…

When Google's Storage Access Framework was introduced, it did not feature a move command, so file managers just resorted to copying and deleting files within the same storage. Not only does this cause needless wear and is much slower, but it also destroys the date/time attribute (it gets changed to current).

When moving files through MTP (miserable transfer protocol, used for connecting smartphones to PC), they are also copy-deleted. This makes moving a 20-Gigabyte DCIM folder impractical. Also, if one cancels the operation, it might end up whoopsie-daisy deleting some files from the source before they have been transferred.

MTP is so bogus that it is incapable of a simple operation that would JustWork™ on mass storage devices. Not to mention, MTP lacks parallelism and its directory listing loading it S-L-O-W. Upwards of a minute for just 1000 files. Sometimes, it fails loading at all.

Also, trying to rename a file through MTP using the terminal through GVFS, even if just within the same folder, it copy-deletes it. If I want to rename a 1 GB 2160p 4K video in a highly populated DCIM folder, I can not do so through the terminal. At least, the 4K video has a time stamp in its internal metadata, but it still renames slowly and adds needless wear to the smartphone's flash memory.

Whoopsie!

collected seeds from a plant that showed up in my garden this year

you can make some psychedelics from the seeds. if you remove the poison.

anyway my hands feel weird. whoopsie. feels more like poison than a nice psychedelic trip smh