Comments on: Three Qualities that Every Piece of Code Should Have … http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/ Sun, 14 Mar 2010 12:04:09 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Elegant Code » Ethics in Software Development: Craftsmanship over Crap http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/comment-page-1/#comment-42593 Elegant Code » Ethics in Software Development: Craftsmanship over Crap Sun, 11 Jan 2009 18:36:56 +0000 http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/#comment-42593 [...] Robert C. Martin calls ‘Craftsmanship over Crap’ the fifth principle of the agile manifesto. I’ve been writing a lot on this blog about writing clean code and qualities that every piece of code should have. [...] [...] Robert C. Martin calls ‘Craftsmanship over Crap’ the fifth principle of the agile manifesto. I’ve been writing a lot on this blog about writing clean code and qualities that every piece of code should have. [...]

]]> By: vishwajeet singh http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/comment-page-1/#comment-28606 vishwajeet singh Wed, 30 Jul 2008 08:32:35 +0000 http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/#comment-28606 Nice post Nice post

]]> By: Dew Drop - July 29, 2008 | Alvin Ashcraft's Morning Dew http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/comment-page-1/#comment-28545 Dew Drop - July 29, 2008 | Alvin Ashcraft's Morning Dew Tue, 29 Jul 2008 13:26:44 +0000 http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/#comment-28545 [...] Three Qualities That Every Piece of Code Should Have (Jan Van Ryswyck) [...] [...] Three Qualities That Every Piece of Code Should Have (Jan Van Ryswyck) [...]

]]> By: Davy Brion http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/comment-page-1/#comment-28530 Davy Brion Tue, 29 Jul 2008 09:18:24 +0000 http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/#comment-28530 true, but when it comes to the presence of tests, i'd rather be as explicit as possible ;) true, but when it comes to the presence of tests, i’d rather be as explicit as possible ;)

]]> By: Jan Van Ryswyck http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/comment-page-1/#comment-28515 Jan Van Ryswyck Tue, 29 Jul 2008 05:12:40 +0000 http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/#comment-28515 Agreed, but I actually implicitly applied that by the second point. Code that is easy to change, in my view, also has a good ecosystem around it (CI, unit tests, acceptance tests, code analysis, etc. ...) Without this implicit thinking, its true that something that is easy to change doesn't necessarily need be easy test. Agreed, but I actually implicitly applied that by the second point. Code that is easy to change, in my view, also has a good ecosystem around it (CI, unit tests, acceptance tests, code analysis, etc. …) Without this implicit thinking, its true that something that is easy to change doesn’t necessarily need be easy test.

]]> By: Davy Brion http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/comment-page-1/#comment-28488 Davy Brion Mon, 28 Jul 2008 21:11:49 +0000 http://elegantcode.com/2008/07/28/three-qualities-that-every-piece-of-code-should-have/#comment-28488 there is one quality that i'd add to the list: it should be easy to test code that is easy to test is often easy to change, and should 'work'. However, code that is easy to change and that works is not always easy to test :) there is one quality that i’d add to the list:

it should be easy to test

code that is easy to test is often easy to change, and should ‘work’. However, code that is easy to change and that works is not always easy to test :)

]]>