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.
I chortled. Well done.
Fuckin’ A
Fuck off
Fuck U
are you a fellow alumni?
I curse at my code. Does that count?
I think the study demonstrates that you’re cursing at your code because you’re not cursing in your code.
Well, fuck.
No, no, like this:
// Well, fuck.
/* Well, fuck */
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
in conclusion, remember to always curse in your comments because it will make your code better
I can only read ‘swearwords’ - non-hyphenated and juvenile - so many times before I’m done.
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.
Or don’t know how to look at a code repo.
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.
Fuck yeah.
Never read something more stupid.
