Man, at $DAYJOB, if we open-source something, they tell us to check for checked-in passwords and whatnot, and force us to throw away the commit history, which always feels stupid when we've known upfront that we're going to open-source it and so kept things clean from the start.

But then, yeah, you see a post like that and just think that it really wouldn't have been too difficult to search for swear words before publishing.
I mean, I also don't really care, since it's code rather than an official communication channel, but I can understand why management might care.

[–] SpaceNoodle@lemmy.world 87 points 23 hours ago (2 children)

Management can go fuck themselves. Do they want the code to fucking work or not? These are load-bearing fucks.

[–] wheezy@lemmy.ml 15 points 15 hours ago* (last edited 15 hours ago)

It literally helps future programmers. There is nothing more inspiring than reading comments you can feel solidarity with. These literally are load bearing comments.

I also enjoy the sarcastic "I won't regret taking this shortcut" comments. Like, you're trying to fix some ass-holes code and they are literally mocking you for the fact that they knew they did it wrong but it would be someone else's problem in the future. It's a "pass the torch" kind of thing that I always enjoy. Like, I can't be mad because I just feel so connected in our mutual frustration of wage labor bull shit.

[–] KeenFlame@feddit.nu 6 points 17 hours ago

The day I cannot swear in my code is the day I auto obsfuscate the whole thing so I can continue using swearwords but now also nobody else can work the code