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

Kevlin: Take Time to Read Other People's Good--and Bad--Code moved to Take Time to Read Other People's Good (and Bad) Code

2009-07-19T23:54:45Z

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

←Older revision

Revision as of 23:54, 19 July 2009

Clarman at 11:41, 13 July 2009

2009-07-13T11:41:07Z

←Older revision		Revision as of 11:41, 13 July 2009
Line 1:		Line 1:
	How do we become better programmers?		How do we become better programmers?
-		+	<br>
		+	<br>
	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.		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.
-		+	<br>
		+	<br>
	Try it, over a tea break.		Try it, over a tea break.
-		+	<br>
		+	<br>
	Ask unfamiliar people for examples of their code that they think is worth reading.		Ask unfamiliar people for examples of their code that they think is worth reading.
-		+	<br>
-	Ask 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).	+	<br>
-		+	Ask people for examples of their own or other's code that is only worth reading for its smelliness. (Offer to share your dirty laundry with them, to break the ice).
		+	<br>
		+	<br>
	Go to Google Code or SourceForge, and spend 15 minutes reading something that interests you.		Go to Google Code or SourceForge, and spend 15 minutes reading something that interests you.
-		+	<br>
		+	<br>
	Try "pair reading" with a friend, commenting to each other your opinions.		Try "pair reading" with a friend, commenting to each other your opinions.
-		+	<br>
		+	<br>
	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.		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.

Clarman at 11:32, 13 July 2009

2009-07-13T11:32:26Z

←Older revision		Revision as of 11:32, 13 July 2009
Line 5:		Line 5:
	Try it, over a tea break.		Try it, over a tea break.

-	As unfamiliar people for examples of their code that they think is worth reading.	+	Ask 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).	+	Ask 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).
		+
		+	Go to Google Code or SourceForge, and spend 15 minutes reading something that interests you.
		+
		+	Try "pair reading" with a friend, commenting to each other your opinions.

	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.		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.

Clarman: New page: 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 ...

2009-07-13T11:31:06Z

New page: 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 ...

New page

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.