As a culture we are highly focused on results and less so on the path to the result. You can see this mentality throughout our laws.
For example given two drunk drivers going home, the first driver gets caught and recieves a DUI, while the second driver as a result of being drunk hits and kills another driver will get charged with both a DUI and manslaughter. Now both drivers took the same risks and for chances not under their control had two different results, while we can morally blame both drivers for the same actions we choose to punish them differently. This is refered to as resultant moral luck, are you building your software with it?
Just because you delivered software last time that was on schedule and worked correctly, was it just moral luck? Knowing that there are ways to improve your development process and improve your code quality as to reduce the risk involved in creating software, are you still not using them? Not using them is not calling your friend to drive you home from the bar, yes you know its a good idea but you got home safely last time so you don't need to this time.
Should you be accepting moral praise for a project from the business, when the result was less in your control then it could have been? Clearly building a trivial website for a hobby has minimal risk but if the software you are building for a business is of importance, must you wait for a the dice to come up against you before you try to do better?
By Dasha
By tom
By code de la route gratuit
By LINK: What Should I Look For In A Software Development Mentor? | Kansas City Network Professionals
By Jeff Skistad