All the Perl that's Practical to Extract and Report
use Perl Log In
lilstevey (4628)
lilstevey
(email not shown publicly)
Consumes:
(email not shown publicly)
Consumes:
- Heinekin
- Kro
- Addlestones
- Old Rosie
- Thatchers
- Strongbow
- Erdinger
- Guiness
- Budvar
- Leffe ( usually blond )
- Various Real Ales when in premises suitable
Saturday December 08, 2007
03:40 PM
Swearing in comments - what's the opinion now?
I've seen various articles on the web in the past expressing the opinion that placing swear words in comments should not be a reflection of the programmers profesionalism.
I haven't seen these sort of articles released recently, though have on occasion heard opinions stressed that its ok.
As a general case, I'm of the opinion that as a programmer you are responsible for quality of the entirity of your conribution, which you perform in exchange for your salary.
What the customer/employer decides to do with that code, unless expressed otherwise in the contract is totaly their business - not that of the employees.
Therefore, should the business decide to release the source code for the product, the comments become as public as the user interface.
This leads me to suspect that if I am right in suspecting that "cussing in comments" is passe, the commercialisation of open source could be a contributory factor - or perhaps its just a reflection of the maturity of the industry?
Or maybe I'm wrong, and there is still a belief that delivery of code is limtied to user experience.
Either way I'd be interested in the prevailing attitude towards what people percieve is a professional attide to software development. I'd also be interested if people have the same attitude to code released personally to that developed under contract?
I haven't seen these sort of articles released recently, though have on occasion heard opinions stressed that its ok.
As a general case, I'm of the opinion that as a programmer you are responsible for quality of the entirity of your conribution, which you perform in exchange for your salary.
What the customer/employer decides to do with that code, unless expressed otherwise in the contract is totaly their business - not that of the employees.
Therefore, should the business decide to release the source code for the product, the comments become as public as the user interface.
This leads me to suspect that if I am right in suspecting that "cussing in comments" is passe, the commercialisation of open source could be a contributory factor - or perhaps its just a reflection of the maturity of the industry?
Or maybe I'm wrong, and there is still a belief that delivery of code is limtied to user experience.
Either way I'd be interested in the prevailing attitude towards what people percieve is a professional attide to software development. I'd also be interested if people have the same attitude to code released personally to that developed under contract?
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
comp.lang.misc flooded with them, but I don't think that would help the
advance of civilization. :-)
--Larry Wall in <1992Mar5.180926.19041@netlabs.com>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
"There's a Perl script for that..." (Score:1)
A Cautionary Tale:
My op
cursing in code (Score:1)
rjbs
Oops (Score:1)