The invisible thin line…

So do you expect a software guy to figure out the existence of a thin invisible line on the road where parking becomes illegal. I certainly did not and as I come out of my office at 9 at night appreciating the fine regex capabilities of Perl and suddenly I don’t find my bike downstairs. I am a bit confused and lost and call up my wife just to check if I really came on a bike to office. Looks like I did.

The security guard in his Nepali accent tells me that your bike might be in Ashok Nagar Police Station. It was tough for me to figure out form his accent that he was pointing me towards Shock Nagar or Ashok Nagar. Anyway got an auto and headed for the police station. Finally when I got the first view of my bike, I realized it I loved it more than I thought I did. The red pulsar reminded me all the good times I had with it and the day when I did 110 km/per hour on it. Anyway all is well that ends and I am back on my bike feeling the Bangalore breeze.

BTW as far as the thin invisible line is concerned, I hope these cops will at least address the visible part. But isn’t that true in software and life. We have so many invisible thin lines around us all the time. In the software world how to find the thin line between over engineering and under engineering, how to make a user interface with enough content and still load fast enough, do I need Oracle for my needs or a mysql or BDB is enough.  In real life do we bribe the traffic cops for convenience or not, do we give money to beggars on the street or not, do we rip that DVD and see it or not.

I guess both personal as well as professional life presents us with enough thin invisible lines so I should rather not bother about the traffic cops who picked up my bike.

PS: I do use the parking lot now.