Re:What Happens When You Swear At Your Users
by jacques_chester on Monday February 06, 2012 @05:43PM
(#3559567)
Once I left a comment in a source file of the following form.
# This comment included for the benefit of those grepping for swear words: shit.
I don't think I'd do it today, but I was young and it was for a place that had demotivational posters hanging in their lobby.
Re:What Happens When You Swear At Your Users
by bengl3rt on Tuesday February 07, 2012 @01:26AM
(#3560713)
I once worked somewhere that had a poster on the wall: "Meetings - none of us is as dumb as all of us."
I think it was a good reminder.
Re:What Happens When You Swear At Your Users
by DarkShikari on Monday February 06, 2012 @02:24PM
(#3558778)
I think it's not just "strong wording", but the inarticulateness of the first example comment. You can express strong feelings while still being articulate.
Example 1: //FIXME: This code is shit, someone make it better.
Example 2: //FIXME: This code is a truly atrocious hack to work around $issue. I don't know of a better way, but suggestions welcome.
Re:What Happens When You Swear At Your Users
by astine on Monday February 06, 2012 @03:46PM
(#3559111)
Whats the different between example two and this:
//FIXME: This code is a shitty hack to work around $issue. I don't know of a better way, but suggestions welcome.
This contains the same information but uses a swearword. I think that every would agree that clearer comments are better, but does the presence of obscenities inhibit clarity or are they merely offensive and superfluous?> but does the presence of obscenities inhibit clarity
That entirely depends on your work environment. Will adding in obscenities will rouse up some big HR kerfuffle? Then don't do it, you're just wasting everyone's time. Otherwise, do whatever you want.
When I was young, I sometimes couldn't resist the urge to put strong wording in comments, like:
Invariably, when I revisited the code months or years later, I thought by myself: Why swearing? You can also express disagreement in a more neutral way.So, nowadays I use a better commenting style for bad code and tech debts, always with a motivation along it: