If an organization, whether IT-related or non-IT related, hires a pool of programmers, one might closely think how these programmers will be able to work in good harmony and coordination. If they do not follow best team practices and the team is just relatively new, the natural tendency would be that they work very limited only to their own duties, concerned about how they did their work. They might fear for the loss of their jobs, encouraging competition and comparison among them, thus leading them to lesser productivity and ownership.
So, the question here is this: should an organization conceptualize and implement “house rules for programmers?” I see that some might go against it, saying that their way of doing things has been for long time already and it has been working since then. While the others are for it because their concern is for continuous improvement.
How should house rules be implemented then? Does it involve attendance ? performance appraisal? Does it need to be specific in terms of coding practices?
I guess I should leave this issue open-ended so I can gather comments and suggestions. I am about to form our own house rules at work.
Tags: coding practices, house rules, programmers, team, work
I don’t know what kind of “rules” you have in mind, but the key question to me is: What do you want to accomplish? Only then you can decide what the best way is for it (and whether it is some new “rules” or something else).
Daniel,
Thanks for your comment.
You have a point there. Actually, I don’t have anything in mind yet, but I am sure to require other programmers to learn how to use cakephp as well as part of the house rules.
That’s first priority.
Interesting ideas here Jojo. I guess some house rules will include communication protocol, fostering peer review culture, retrospective on tasks assigned/done (what worked well / how could it be done better).
Your idea seems perfect fit as one of house rules! Communication among programmers develops better teamwork.
Peer review is also great idea!