tag:blogger.com,1999:blog-15558048.post8705256047213249995..comments2023-10-12T09:10:31.269-04:00Comments on Modern Software Development Fun: What drives my designing in TDDAnonymoushttp://www.blogger.com/profile/10695648911502574065noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-15558048.post-87461424433045337412010-08-31T12:23:05.483-04:002010-08-31T12:23:05.483-04:00Yes, readability could be subjective. If you have ...Yes, readability could be subjective. If you have an agile team structure which does the following, it might help. <br />1) reasonably team size (less than 10 pairs)<br />2) pair programming<br />3) rotate pair frequently - ideally every developer works on every part of the project<br />4) all team members sits in the same space so that unreadable code being called out easily<br />With this structure, developers will gradually gain the understanding on what kind of code can be deemed as readable in this project. I should probably start another blog entry about this.Anonymoushttps://www.blogger.com/profile/10695648911502574065noreply@blogger.comtag:blogger.com,1999:blog-15558048.post-51144509826695027052010-08-31T12:06:28.516-04:002010-08-31T12:06:28.516-04:00On your point "the code is unreadable," ...On your point "the code is unreadable," I find very few if any of the developers I work with that are able to recognize that characteristic. They wrote it, it makes perfect sense to them, it is even transparently obvious. It takes some person not associated with the development to realize what is or is not readable.Anonymousnoreply@blogger.com