Breaking the rules
Scenario 1 – You approach a 4 way stop sign, with exceptional visibility in all directions. You have to decide if you will roll through the stop sign, or be a ‘good driver’ and come to a full stop. Since you see no benefit in fully stopping you decide to roll on through. As you drive on a motorcycle officer pops out from behind a bush and writes you a ticket for not complying with the law.
Scenario 2 – You need to finish a new feature on a project, so evaluating the design options and impact of them. You can either follow the standard approach that your team uses or save half the time and implement it in a much simpler way. After realizing half the effort for the same effect is the best value for the customer you decide to use the simple implementation. As you finish up and commit your changes into source control, the commit notification alerts the resident ‘architect’ and they scold you for not following standards.
The point I am trying to convey is that rules/standards should only be in place to help people that need guidance, either from a lack of knowledge, or lack of a clear choice. Unfortunately the inflexible nature from the bodies of governance stem from a lack of trust. If you don’t have trust in your developers decisions making capabilities then you have a broken system, and your rules are more constraining then they are helpful.
To sum it up in one line, if you are familiar with the Serenity Prayer then this format might sound familiar…
Grant me the serenity to follow the rules, courage to defy the rules , and the wisdom to know when to do which.
Share Our Posts
Share this post through social bookmarks.
Comments
Tell us what do you think.
Trackbacks
Websites mentioned my entry.
There are no trackbacks on this entry
Yip… rules are for those whose judgment is suspect so the rest of us have to pay.
It always amazes me too, that people only start to pay attention when they come to a stop sign – as if that’s their signal to wake up and see if there’s anyone else on the road. You should be paying attention ALL the time, and more than half of 4-ways stops should be yields – but again, that would beg that the driver is paying constant attention.
You can tell a lot about people by the way the drive…
A better call would be roundabouts as they are in other countries – traffic keeps moving, and drivers pay attention. But then again, how would our law enforcement agencies generate enough capital for their retirement plans?
You sound like a trouble causer. Next time pick up the phone and discuss it with the architect or just be a good team player and do your job properly! If everyone took your approach you would end up in right mess. And next time don’t be so optimistic with your quote and you won’t find yourself in such a mess when it comes to implementing it
Ideally you are correct, good communication is key. As a consultant sometimes I can find myself in a client with a dysfunctional team, when I wrote this post I was dealing with a “senior” developer at the client that didn’t have any interest in talking about new techniques until he noticed them after screening the commits. On big decisions this is obviously something you have to deal with and get discussion about it, but on the smaller scale you need give your developers some room to make independent decisions. And yes for the record I try to be a bit disruptive