Comments on: Ethics In Software Development: Pragmatism Over Dogmatism http://davybrion.com/blog/2009/01/ethics-in-software-development-pragmatism-over-dogmatism/ Trying to walk that thin line between intelligence and ignorance Mon, 15 Mar 2010 08:03:58 +0100 http://wordpress.org/?v=2.9.2 hourly 1 By: Ibrahim Levent http://davybrion.com/blog/2009/01/ethics-in-software-development-pragmatism-over-dogmatism/comment-page-1/#comment-7652 Ibrahim Levent Wed, 14 Jan 2009 16:21:41 +0000 http://davybrion.com/blog/?p=845#comment-7652 Schedule pressure may sometimes force us to make some "Quick-dirty fixes". When I do this, I just mark the code for later correction(With a tag like "REMIND: Fix better"). Later I search these marks and try to fix in a better way. Some refactorings(Large code changes) may also eliminate these qirty conditions. It is much more probable that we find a better way if we give time for it. Later clean fix may be better than initial clean fix with the cost of remembering problem context again. Schedule pressure may sometimes force us to make some “Quick-dirty fixes”. When I do this, I just mark the code for later correction(With a tag like “REMIND: Fix better”). Later I search these marks and try to fix in a better way. Some refactorings(Large code changes) may also eliminate these qirty conditions. It is much more probable that we find a better way if we give time for it. Later clean fix may be better than initial clean fix with the cost of remembering problem context again.

]]> By: efdee http://davybrion.com/blog/2009/01/ethics-in-software-development-pragmatism-over-dogmatism/comment-page-1/#comment-7622 efdee Tue, 13 Jan 2009 13:51:16 +0000 http://davybrion.com/blog/?p=845#comment-7622 I think the problem is that ultimately it is the developer who has to make the call as to whether or not to implement a clean fix or a quick fix, and whether or not he makes the right choice boils down to how skilled he is. I definitely agree with the example you give and I assume you are able to make the right choices because you have a solid education in software development. Maybe I just don't like the word 'pragmatism' because for too much people it is just an excuse to go the quick fix route. I think the problem is that ultimately it is the developer who has to make the call as to whether or not to implement a clean fix or a quick fix, and whether or not he makes the right choice boils down to how skilled he is. I definitely agree with the example you give and I assume you are able to make the right choices because you have a solid education in software development.

Maybe I just don’t like the word ‘pragmatism’ because for too much people it is just an excuse to go the quick fix route.

]]>