There's been a healthy debate over on the software craftsmanship mailing list about what craftsmanship means in the context of software development. I've been a proponent of, among other things, some set of standards by which a practitioner's capabilities can be measured. That's been unpopular, as you might imagine.
Tuesday, January 18, 2011
Wednesday, January 12, 2011
Documentation in the wild
I just started a new project. I has no documentation except the code.
In this particular project, this is generally a Good Thing--the code in question is clear, well written, and (ahem) completely without comments. I'm not having a lot of trouble understanding it, overall, because it really is very good code. But... I've spent 2 days trying to figure out how one important feature works.
http://thedailywtf.com/Articles/Documentation-Done-Right.aspx
'Nuff said.
In this particular project, this is generally a Good Thing--the code in question is clear, well written, and (ahem) completely without comments. I'm not having a lot of trouble understanding it, overall, because it really is very good code. But... I've spent 2 days trying to figure out how one important feature works.
http://thedailywtf.com/Articles/Documentation-Done-Right.aspx
'Nuff said.
Subscribe to:
Posts (Atom)