Everyone wants clean code. We have learned early on in our careers that bad code is a monster eating away at our project deadlines. The question this article is trying to answer is if it's possible to set up a development process in a way that will, by design, prevent the rotting of our source code.
Introduction
Let's just get one thing straight. There is always a point in a project where someone has to decide to do things quick and messy, and then, later on, pay the price. This is OK from a tactical point of view. But it is possible to set up tools that will let us keep code quality standards even in cases of quick and dirty code writing
from DZone.com Feed http://bit.ly/2MJ8Hws
No comments:
Post a Comment