Wednesday, January 25, 2012

coding standards

I received an email from the consulting partner company who is the lead on the project referenced in the post from yesterday (1/24/2012) regarding coding standards...

Attention to all [company name redacted] developers, [software company redacted] technicals, and [software company redacted] functionals writing or specifying code:


Your performance and evaluation will be based, in part, on how well you follow the standards and how your code performs.

If, during a code review, your code does not follow these guidelines, you will be required to modify your code on your own time after [company name redacted]'s normal business hours.

Following these standards is a condition of employment at [company name redacted]

...(blah, blah, blah)...

Thank you,

Human Resources Department
[company name redacted]

Where to begin? Maybe from the signature signed from the HR department discussing coding standards requirements. I haven't found much use for HR departments in general, and I usually find them rather inert, but to hold coding standards accountable as a condition of employment? Really?

I think my favorite part is where coding standards will be your responsibility outside of "normal business hours." This begs the question of what are the "normal business hours?" When I was a young consultant, that meant from 8a.m. until 11p.m. or later Monday through Friday and 8a.m. to 6 or 7p.m. on Saturdays and Sundays. (Even now I have "office hours" between 8a.m. and 5 or 6p.m. but am online and busy starting about 6a.m. and ending whenever I can safely go offline without leaving someone waiting on a response.) I'll give them that coding standards are important, yet one of the first items cut in a project timeline is documentation, followed by testing. Nice way to make sure the coding is done correctly without having to pay for it.

No comments:

Post a Comment