this post was submitted on 02 Oct 2024
279 points (97.3% liked)

People Twitter

8867 readers
1232 users here now

People tweeting stuff. We allow tweets from anyone.

RULES:

  1. Mark NSFW content.
  2. No doxxing people.
  3. Must be a pic of the tweet or similar. No direct links to the tweet.
  4. No bullying or international politcs
  5. Be excellent to each other.
  6. Provide an archived link to the tweet (or similar) being shown if it's a major figure or a politician. Archive.is the best way.

founded 2 years ago
MODERATORS
all 21 comments
sorted by: hot top controversial new old
[–] corroded@lemmy.world 58 points 1 year ago (1 children)

I like to leave un-commented lines of vulgar text in my code when it's time to call it a day but I'm still working on solving a problem.

Then the next day, when I try to compile, I get an error for "This fucking shit-ass function should be returning 64 instead of 128, but I'm a dumbass and write shit code" not being valid syntax.

It's a great way to leave a reminder.

[–] TheOneAndOnly@lemmy.world 3 points 1 year ago

I chortled. Well done.

[–] OpenStars@discuss.online 18 points 1 year ago
[–] Ersatz86@lemmy.world 17 points 1 year ago (1 children)
[–] ininewcrow@lemmy.ca 2 points 1 year ago (1 children)
[–] Ersatz86@lemmy.world 2 points 1 year ago (1 children)
[–] ininewcrow@lemmy.ca 1 points 1 year ago

are you a fellow alumni?

[–] hperrin@lemmy.world 15 points 1 year ago (1 children)

I curse at my code. Does that count?

[–] Balthazar@lemmy.world 10 points 1 year ago (1 children)

I think the study demonstrates that you're cursing at your code because you're not cursing in your code.

[–] hperrin@lemmy.world 2 points 1 year ago (1 children)
[–] WanakaTree@lemm.ee 3 points 1 year ago (1 children)

No, no, like this:

// Well, fuck.

[–] OpenStars@discuss.online 2 points 1 year ago

/* Well, fuck */

[–] grue@lemmy.world 12 points 1 year ago

Subsequently, we quantified the adherence of these two distinct sets of source code to coding standards, which we deploy as a proxy for source code quality

LOL

[–] hanke@feddit.nu 10 points 1 year ago
[–] affiliate@lemmy.world 7 points 1 year ago

in conclusion, remember to always curse in your comments because it will make your code better

[–] shasta@lemm.ee 6 points 1 year ago (1 children)

So basically, if there are curse words in your comments it probably means that the people calling the shots on the project care more about the code being functional and maintainable than policing political correctness of the comments.

[–] OpenStars@discuss.online 4 points 1 year ago

Or don't know how to look at a code repo.

[–] corsicanguppy@lemmy.ca 5 points 1 year ago

I can only read 'swearwords' - non-hyphenated and juvenile - so many times before I'm done.

[–] Aceticon@lemmy.world 3 points 1 year ago

I spontaneously curse at it, in 4 different (spoken) languages even and abundantly so at times, but I don't feel the need to actually write down the swear words.

Writting it down just doesn't feel the same as merelly just letting out those expletives that naturally arise during the making (and, especially, testing) of software.

[–] Etterra@lemmy.world 2 points 1 year ago