Monday, December 13, 2010

Hate reading others' code?

Most of us hate reading others' code and we have reasons for the same. Our primary concern is that each has his/her own style of writing which we may or may not adapt, ultimately leading to waste of valuable time and energy. And if there is no proper documentation, there is NO question about reading it.
But things are different in real time. World is moving so fast and it doesn't wait till we re-invent the wheel. So like it or not, we are *forced* to read others' code.
So I thought of 'googling' for some tips. One of the posts that I found interesting as well as useful is this.
One of the eye-opening facts exposed in the post is, "Reading great code is just as important for a programmer as reading great books is for a writer" - You cannot write a good book without reading books written by great writers. So to become a professional coder, you need to check out code written by others.
The post also contains good techniques of how to start with reading a code base. I found it really helpful and I wanted to share it to all. Thanks to Skorkin for the great post!


Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. --Brian Kernighan

1 comment: