Tag Info

New answers tagged

0

Unit tests and Integration tests can be used to protect your logic from code changes. If you currently have a good code coverage, and you need to re-work a section, then the approach would be easier, you can change your tests to reflect the result after the re-work and once you have done the change you can re-run the test cases, to make sure it's all ...


-1

It's never nice when things change, hope it hasn't got you down though. I do the architecture for our company as well and have asked some similar questions, so will share the little bit I know. Firstly I've found that there is no realistic solution for massive changes. The solutions I did find meant that everything had to be built so dynamically, that it ...


3

The only thing you can do to help reduce the impact of a change is to split your overall project up into many components, so while a major change will impact several of them, many will not be affected. eg if the customer decides they need a new button that sends data through the middletier to be stored in a new column in the DB, you're going to have to ...


0

The most maintainable code is code that isn't there. So instead of adding to the LOC count, new code that 'reduces' the LOC count (even if slightly less maintainable when viewed in isolation) could make the total code-base more maintainable simply by reducing its size. Thus the primary rule for maintainable code: maximize DRY. Secondly, there is nothing ...



Top 50 recent answers are included