{"id":12102,"date":"2014-05-16T14:52:36","date_gmt":"2014-05-16T11:52:36","guid":{"rendered":"https:\/\/mozaicworks.com\/?p=7042"},"modified":"2014-05-16T14:52:36","modified_gmt":"2014-05-16T11:52:36","slug":"the-good-the-bad-and-the-ugly-code","status":"publish","type":"post","link":"https:\/\/mozaicworks.com\/blog\/the-good-the-bad-and-the-ugly-code","title":{"rendered":"The Good, the Bad and the Ugly code"},"content":{"rendered":"

Not long ago, one of my colleaques asked me what is the way that helps me more to learn. My quick answer was “Through stories”. I was sure about it because I have an experience to confirm it. This experience was the talk that Rebecca Wirfs-Brock<\/a> have given last year at I TAKE Unconference<\/a>. It was my first attendence to a keynote talk, the first time I was in front of an international software craftman and the first time I saw code from international big projects like “NASA X-ray Telescope InFOC\u03bcs” and Javascript. She had presented the code while telling us stories about it and these two were not the only ones. I will do a quick summary of all of them and of what I have learned.<\/p>\n

The Good: A Story of Consistent Error Reporting Evolution<\/h2>\n

With this story, Rebecca taught us how to deal with good code. By showing us how the code evolved with each sprint, what design decisions they took, what mistakes they made and how they solved them, she succeded to print into my mind the following quotes:<\/p>\n

Sometimes if you want to see a change for the better, you have to take things into your own hands. – Clint Eastwood<\/em>
\n Good code is its own best documentation. – Steve McConnell<\/em>
\n Good code is not beautiful code. – Rebecca Wirfs-Brock<\/em>
\n If the windows are not repaired, the tendency is for vandals to break a few more windows. – “The Broken Window Theory”, James Q. Wilson and George L. Kelling<\/em><\/p><\/blockquote>\n

More, for each quote there is a good coding practice to follow:<\/p>\n