http://www.elilopian.com/2009/06/11/will-liability-change-everything/ Creating better software Fri, 20 Aug 2010 20:27:04 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://www.elilopian.com/2009/06/11/will-liability-change-everything/comment-page-1/#comment-39497 Eli Lopian Sun, 14 Jun 2009 09:20:25 +0000 http://www.elilopian.com/2009/06/11/will-liability-change-everything/#comment-39497 True, Lets define a sloppy doctor, he could be a doctor that has a different understanding of how to cure people, he might believe in a specific procedure or not, I am sure that he cares about what he does. That (the caring), does not exempt the doctor from liability if he make a mistake. A mistake is being sloppy, not performing the correct action. So what are the actions that a *software developer* has to perform to be except from liability. True,
Lets define a sloppy doctor, he could be a doctor that has a different understanding of how to cure people, he might believe in a specific procedure or not, I am sure that he cares about what he does. That (the caring), does not exempt the doctor from liability if he make a mistake. A mistake is being sloppy, not performing the correct action. So what are the actions that a *software developer* has to perform to be except from liability.

]]> http://www.elilopian.com/2009/06/11/will-liability-change-everything/comment-page-1/#comment-39305 Andy Stopford Thu, 11 Jun 2009 23:13:49 +0000 http://www.elilopian.com/2009/06/11/will-liability-change-everything/#comment-39305 Do we first define 'sloppy' developer? Sloppy could mean lazy or could mean petulant, it could mean differnt things to different people. Some developers believe in TDD and unit testing, some don't. Some developers can write code with out any or few bugs with no unit tests. Code with even the greatest unit test and code coverage stats can still have bugs (business logic erros and non testable areas cheif amongst them). A developer can still care about what they do but not believe in unit tests and that does not make them a sloppy, lazy or even a bad developer. What makes a bad developer is one that does not care about what they do and I doubt that such a developer really exists. What prehaps needs to happen is for our industry to develop quality standards based on measureable stats, unit tests, code coverage, exposure of tests over rules and business process (such as BDD and FIT say). The measures of test between unit to integration to functional to system test is often lost in the translation and our industry could very well develop standards that show that this takes effect. If our industry can then show this quality control takes effect in products as say a kite mark then this would give the consumer the convidence. Do we first define ’sloppy’ developer? Sloppy could mean lazy or could mean petulant, it could mean differnt things to different people. Some developers believe in TDD and unit testing, some don’t. Some developers can write code with out any or few bugs with no unit tests. Code with even the greatest unit test and code coverage stats can still have bugs (business logic erros and non testable areas cheif amongst them). A developer can still care about what they do but not believe in unit tests and that does not make them a sloppy, lazy or even a bad developer. What makes a bad developer is one that does not care about what they do and I doubt that such a developer really exists. What prehaps needs to happen is for our industry to develop quality standards based on measureable stats, unit tests, code coverage, exposure of tests over rules and business process (such as BDD and FIT say). The measures of test between unit to integration to functional to system test is often lost in the translation and our industry could very well develop standards that show that this takes effect. If our industry can then show this quality control takes effect in products as say a kite mark then this would give the consumer the convidence.

]]>