Tuesday, 6 June 2006

Lip service has negative value

I feel that lip service has negative impact on all the things that you do. It's worse than not saying anything at all. Specifically I am talking about processes at your job.

Let's make up an example. Let's say you have 2 processes, people have to: 1) check tests in with their code and 2) write their name on the whiteboard as the last person that checked code in.

Arguably process #2 might not be as useful. So people stop doing it consistently. Then it stops being done at all. New people come join the group and have to learn what processes are done, which ones are bent, and which ones are ignored. I think that this leads to a thought process of "well, if process #2 is optional, maybe #1 is as well". Ignoring one process is a broken window and will quickly lead to more being ignored.

If you have a process, there has to be some kind of audit or automated check. If there isn't, that means it has to really make sense why you are doing it so that it's not really a process, it's just "the way things are done". For processes without audits or 100% buy in, you have to question why you actually have it if it's not important enough to check that it is being followed.

I think that for all processes, every once and a while you should be asking yourself:
  1. does this process still make sense in our current env
  2. how much value does it bring
  3. how much does it cost
  4. could we be doing a different process for a greater ROI


If you have a process that is almost universally ignored, all that you are doing is weakening the other processes. It's a strange case where the whole is less than the sum of the parts. Back to our example, rather than having said anything about process #2, it's better to not have said anything at all rather than risk that people start to not check in tests with the code. But with that process, if there is no audit, no enforcement, that too will soon be an "optional" process. No matter how strong the process, there must be someone around to check for cracks starting before you have a flood on your hands.

Monday, 5 June 2006

Deadline

Check out the second defination of deadline. :-o

Faster, Stronger, Better...

When someone tells me that I am the resident expert of anything, I laugh. Not because of the explanation of what an expert is (an "ex" is a has-been and a 'spert is a drip under pressure), but because I can't seriously see me in any kind of role like that right now.

Don't get me wrong, I like being able to share my knowledge with other people. But to look at the stuff I have done as a shinning example? hahah... No. I can't believe that for the simple fact that I would no longer try and do a better job. I have to believe that I can do my job better. To make my apps faster, stronger, more robust, better tested, easier to maintain.

I can't let my skills stay where they currently are. I have to read more, learn more, do more. There isn't an option.

Saturday, 3 June 2006

My Cubicle

If you work in a cube, you would probably like the song this guy linked to. Pretty funny.

In other news, I'm going to stop using trackback. No one ever tracks back to me (other than Ryan or myself), so I don't seem much point.

Tuesday, 30 May 2006

Dangers of biking to work

The biggest danger biking to work isn't biking in traffic. It isn't the cars, vans, dilivery trucks, buses, or other bikers. It's the people walking along listing to their music. I try not to bike on the side walk, but there are a few places where I have to (along the transit way). Now, I understand why if you're listening to music you might not hear someone ringing a bell. But for frigging sakes stay at one side of the path! And I don't care which one, just pick one!

I think that it would be easier to avoid drunks in the market on Saturday night than "normal" people walking along not paying any attention to the world around them. *sigh*

Monday, 29 May 2006

Happy Year 3!!

It's been 3 years so far... I guess this is the last year that this anniversary will be important... ;-)

Sunday, 28 May 2006

T minus 363 d

We just passed our negitive one year anniversary. Weee!! Needless to say, wedding planning is on our minds. I just find it so weird though... some of the traditions of a "typical" wedding don't feel applicable to us. I guess we're part of the "new norm" of couples living together for a couple of years before tying the knot.

Examples? Well, like not seeing the bride before (or on) the wedding day. Or picking out gift suggestions for "our new life" together when we've already bought everything that we need or use for day to day. What about invitation's? Most communication I have about parties is done with email or by phone. What's so bad about sending out an e-invite for people to come? *sigh* I think that I just don't get it. I know it's a very important day, but sometimes I feel that we're asking the barber if we need a haircut: they'll always say yes.