While I have some sympathy for anyone who loses months of work, as an IT administrator by day, all I have to say about their lack of backups, and lack of RTFM before messing with shit is:

HAHAHAHAHAHAHA HAHAHAHAHA. you got what you deserved fucker. GL.YF.

[–] Homescool@lemmy.world 2 points 1 hour ago

I will RTFM after literally anyone else does.

[–] voldage@lemmy.world 6 points 3 hours ago

Yeah, it's bad enough that it could happen, the fact they allowed that to happen so easily is far worse.

[–] hakunawazo@lemmy.world 5 points 2 hours ago

[–] MonkeMischief 12 points 4 hours ago (2 children)

Man I get paranoid about synchronization programs for this very reason. There's usually some turnkey easy-mode enabled as soon as you first launch that's like:

"Hey you wanna back up your entire NAS to your phone?! That'll be fun, right?!"

And you're like "...No."

And then it wants to obliterate everything so it's all "synchronized", often it's not easy to find a "No, stop, don't do anything at all until I configure this." Option.

iTunes was SO BAD about this.

Syncthing is the least-bad sync software I've ever run. It's got some footguns but it's still brilliant.

I would imagine there's still ways to back up version controlled software right?

[–] mindbleach@sh.itjust.works 1 points 43 minutes ago

iTunes would stomp all over your hard drive, fucking up every MP3 file it could find, and then refuse to believe you could have one copy of a file. Either it's on your iPod and your computer, or it's getting dragged behind the woodshed.

Give me sync software that only ever increases redundancy.

[–] Lifter@discuss.tchncs.de 2 points 3 hours ago* (last edited 3 hours ago)

Any professional would have a code repository and probably a build server which spits out binaries left and right, off site of course.

Bonus points if that is the easiest way to deploy the software, so all developers actually use it.

Edit: typo

[–] Phoenix3875@lemmy.world 34 points 6 hours ago (3 children)

Reminds me of a hilarious bug in early GHC: https://gitlab.haskell.org/ghc/ghc/-/issues/163

The compiler will delete your source file if there's any compile error. And the user complained only by sending a very polite email to report this bug. Simon Peyton Jones mentioned it in one of his talks and I still find it quite hilarious till this day.

[–] fibojoly@sh.itjust.works 8 points 4 hours ago

Left the --hardcore compile option on. Easy mistake.

[–] blarg@programming.dev 6 points 4 hours ago

Software development: hardcore mode

load more comments (1 replies)

[–] burak29@lemmy.cronyakatsuki.xyz 1 points 2 hours ago

"Microsoft Please Fix" ifadesi, genellikle kullanıcıların Microsoft ürünlerinde yaşadıkları sorunlara veya hata bildirimlerine yönelik bir çağrıdır. Tostçu Mahmut Menu

[–] DelightfullyDivisive@lemmy.world 13 points 6 hours ago (1 children)

I'm sure that the "three months of work" was completely shit code. Anybody who is unfamiliar with source control (or even backups!) is prone to making stupid mistakes. Republican voters are likely to have a similar experience over the next 4 years.

[–] xorollo@leminal.space 21 points 6 hours ago

What a delightfully divisive statement. We do all need to start somewhere though, and losing months of work is very discouraging!

[–] bitwolf@sh.itjust.works 29 points 8 hours ago (3 children)

It does warn you it will erase the file when you discard...

[–] JackbyDev@programming.dev 16 points 5 hours ago (2 children)

Go read the actual thread. There was a bug someone found that files you have in there that aren't even associated with git still get deleted. I'm not entirely convinced this was the poster's fault.

[–] bitwolf@sh.itjust.works 1 points 1 hour ago

I did read the whole thread. I also referenced the resolution further down the comment thread.

They've adjusted the error message to be abundantly clear after the fact.

[–] Scoopta@programming.dev 8 points 4 hours ago (1 children)

It's not a bug, it's intentional. They consider changes to be any change since the last commit including in untracked files. They did update it to make this behavior a lot more obvious though.

[–] JackbyDev@programming.dev 7 points 4 hours ago (1 children)

This comment in particular does a great job of explaining the UX problem with this. https://github.com/microsoft/vscode/issues/32459#issuecomment-322160461

[–] Scoopta@programming.dev 6 points 3 hours ago

Yes, honestly this situation reminds me a lot of the LTT trying Linux and destroying his system by installing steam despite apt warning him in the best way it really could that he probably didn't want to do that. Sure the package shouldn't have been in that state in a stable distro but shit happens. It goes to that point of, users will go through great lengths to achieve the end goal blindly jumping past warnings on the way no matter how dire they might be.

[–] kalpol@lemmy.world 14 points 6 hours ago (9 children)

Warns you that changes will be discarded....not quite the same words

load more comments (9 replies)

load more comments (1 replies)

[–] Anticorp@lemmy.world 9 points 7 hours ago

Why are they messing with the source control options when they're not using source control? Perhaps learn about stuff before you start clicking buttons and performing delete operations on your super critical files?

load more comments