Take Time to Read Other People's Good (and Bad) Code

From WikiContent

Revision as of 11:31, 13 July 2009 by Clarman (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

How do we become better programmers?

I've worked with developers who have been programming for many years, but on inspection, their code is smelly. As a pattern, such programmers do not participate in frequent code reviews with new people, to get fresh feedback, and they do not set aside time to just sit down and read code.

Try it, over a tea break.

As unfamiliar people for examples of their code that they think is worth reading.

As people for examples of their own or other's code that is only worth reading for its smelliness. (Other to share your dirty laundry with them, to break the ice).

To obtain a degree in creative writing at university, students spent long long hours, for years, in writers circles in which they share their writing, and get feedback from others. And creative writers are required to read the works of many other writers, and critique it. We need more of this to become better programmers.

Personal tools