Swaroop C H

blog books about contact subscribe

Two nuggets from Coders at Work book

31 Dec 2011

I’ve been reading Coders at Work on and off, and it is a good read for coders who want to learn how coders, who they admire, think and approach programming.

Two favorite nuggets of mine so far are from JWZ and Brad Fitzpatrick who are definitely two of my programming heroes:

About taking things apart

Seibel:

Is there a key skill programmers must have?

Zawinski:

Well, curiosity - taking things apart. Wanting to know what’s going on under the hood. I think that’s really the basis of it. Without that I don’t think you get very far. That’s your primary way of acquiring knowledge. Taking something apart and looking at it is how you learn to build your own. At least for me. I’ve ready very few books about computers. My experience has been digging through source code or reference manuals. I’ve got a goal and, alright, to do this I need to know what this thing does and what this thing does. And I’ll just sort of random-walk through that until I find where I’m going.

How to improve oneself

Seibel:

Do you have any advice for self-taught programmers?

Fitzpatrick:

Always try to do something a little harder, that’s outside your reach. Read code. I heard this a lot, but it didn’t really sink in until later. There were a number of years when I wrote a lot of code and never read anyone else’s. Then I get on the Internet and there’s all this open source code I could contribute to but I was just scared shitless that if it wasn’t my code and the whole design wasn’t in my head, that I couldn’t dive in and understand it.

Then, I was sending in patches to Gaim, the GTK instant-messenger thing, and I was digging around that code and I just saw the whole design. Just seeing parts of it, I understood. I realized, after looking at other people’s code, that it wasn’t that I memorized all my own code; I was starting to see patterns. I would see their code and I was like, “Oh, OK. I understand the structure that they’re going with.”

Then I really enjoyed reading code, because whenever I didn’t understand some pattern, I was like, “Wait, why the fuck did they do it like this?” and I would look around more, and I’d be like, “Wow, that is a really clever way to do this. I see how that pays off.” I would’ve done that earlier but I was afraid to do it because I was thinking that if it wasn’t my code, I wouldn’t understand it.

Comments

babanna duggani says:

Thanks for discussing about various new books. I have learnt a lot from your blog.

Abhishekam N Swamy says:

I liked the Bernie Cossel interview a lot - specially for the 'no problem is inherently hard' advice. Really enjoyed this book a lot.

Ouertani Mohammed Amine says:

I liked the whole fitzpatrick interview

Feedback

There's no comment box, but please do email me or tweet me your thoughts and criticisms, and I will publish the relevant ones here.