Microsoft is full of interesting people. Some of the guys in my group go snowboarding once a week and they are kind enough to take me along and show me the ropes. We usually go to the
I am from
Back to snowboarding. If you haven’t tried it. . . stop what you are doing right now. I mean it stop it. Get in your car, drive up to the mountain and get a snowboarding leason. You will
As you can imagine I am still very much a learner. Even though I spend a lot of time laying in snow trying to figure out how I went from zooming down the mountain (ok. . .ok maybe not zooming) to laying on my butt in the snow, I probably enjoy my time on the mountain more than anyone else.
One of the hardest things for me to learn is “know where the fall line is”. You can think of the fall line as the direction a marble would go (if marbles would roll down the side of a snow covered mountain). The direction you can go and which edge of the board you can use is determined by the fall line. I am constantly seeing a false fall line in the direction I want to travel. It is a form of wishful thinking. I convince myself that the fall line is in a direction compatible with where I want to go and turn accordingly. Of course the brutal laws of gravity show no mercy and I will catch an edge and face plant. So the deal is. . . no matter how much you may want the fall line to be going in a different direction, you have to accept reality and know where the real fall line is.
So how does this apply to programming…..
Know how much you can actual do and don’t over commit. When your manager or teammate ask how many features you can complete or how many bugs you can resolve, know your fall line, and don’t over commit. No matter how much you may
Know where the fall line is.