41–50 of 82 posts
I personally prefer not to swear outright, in code or otherwise, but it's only a preference.
Swearing in comments is unacceptable IMO. You wouldn't write swear words in internal documents, so why do it in code. It's unprofessional and shows a level of dis-respect for your own code and for the people who might end up maintaining it. Plus, heaven forbid a client happened to see it as well.
You work in a corporate environment don't you. You had to fill out a "comment request form" in triplicate just to post the above comment ;) I'd say it depends. If you're working for bigco, swearing is probably not going to go down well with your boss, or co-workers. If you're working in a startup/open source project/on your own, then swearing can be good and useful IMHO. If I swear in the comments of some code (Rare)…
You don't work in a corporate environment, do you?
If you're working for bigco, swearing is probably not going to go down well with your boss, or co-workers
Since few bigcos I've ever worked at ever do code reviews, how would they even know?
After spending many years in corporate environments, it's easy to spot those who haven't when they post comments about corporate environments.
Seriously.
Vista bugs are new, so they are a royal pain in the ass to trace. Microsoft is typically unresponsive at best and in a denial at worst. The most frustrating part is that bugs affect parts that were present in the OS and worked just fine as early as Windows 2000.
Just to give an example - installing a driver or a adding a device instance from a service causes a deadlock in the Setup module that can only be resolved by forcefully terminating the calling process. A deadlock.
They broke basic stuff and these booby traps are sitting in the OS waiting for a dev to step on them. And you bet I am going to leave a comment regarding the IQ of whoever's responsible after I kill two weeks chasing the results of their sloppy coding around this piece of engineering.
Earlier quoted context omitted.
You work in a corporate environment don't you. You had to fill out a "comment request form" in triplicate just to post the above comment ;) I'd say it depends. If you're working for bigco, swearing is probably not going to go down well with your boss, or co-workers. If you're working in a startup/open source project/on your own, then swearing can be good and useful IMHO. If I swear in the comments of some code (Rare)…
You work in a corporate environment don't you. You had to fill out a "comment request form" in triplicate just to post the above comment You don't work in a corporate environment, do you? If you're working for bigco, swearing is probably not going to go down well with your boss, or co-workers Since few bigcos I've ever worked at ever do code reviews, how would they even know? After spending many years in corporate en…
Earlier quoted context omitted.
You work in a corporate environment don't you. You had to fill out a "comment request form" in triplicate just to post the above comment You don't work in a corporate environment, do you? If you're working for bigco, swearing is probably not going to go down well with your boss, or co-workers Since few bigcos I've ever worked at ever do code reviews, how would they even know? After spending many years in corporate en…
My last job was in a corporate cubedom for 4 years. Not a massive company, but a few 100s of employees. We held weekly code reviews at one point. Also bosses do have a habit of suddenly believing that if they help code the project might run quicker, so they ask for svn access etc, then break everything :)
But tell me, when did you ever have to fill out a "comment request form" in triplicate?