Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Scribd will begin operating the SlideShare business on September 24, 2020 As of this date, Scribd will manage your SlideShare account and any content you may have on SlideShare, and Scribd's General Terms of Use and Privacy Policy will apply. If you wish to opt out, please close your SlideShare account. Learn more.
Published on
Every developer has been there--late at night, deadline looming, piling hacks on top of hacks to get a little closer to being finished, there are no tests, edge cases are totally forgotten. Many of us think these situations lead to the worst code we could possibly write. Under such conditions, it is difficult to write robust, well architected code--true--but this is not the only situation that leads to that end. Software development is a complex, creative process that can easily get out of hand. This is because one large factor is often forgotten about--the human factor. Avoiding writing the worst code ultimately comes down to how the people writing, spec'ing, testing, validating, and tracking the code interact.