Skip to main content

Before You Refactor

Refactoring need to be done by every programmer and it leads to have a maintainable code base.Rajith Attapattu has highlighted very good points when doing refactoring

  • The best approach for restructuring starts by taking stock of the existing
    codebase and the tests written against that code.
  • Avoid the temptation to rewrite everything.
  • Many incremental changes are better than one massive change.
  • Many incremental changes are better than one massive change.
  • New technology is an insufficient reason to refactor.
  • New technology is an insufficient reason to refactor.
  • Remember that humans make mistakes.

Other than above, good practices can be found in here.

Labels:

Comments

Post a Comment

Popular posts from this blog

The transaction is in doubt

Sometimes you may get this error when you use transaction scope . The transaction is in doubt I also got this error recently and able to find the reason for it. That is because of the some of the readers had not properly disposed. Actually in this case you can use Using keyword to overcome this. Exception : System.Transactions.TransactionInDoubtException was unhandled by user code Message="The transaction is in doubt." Solution : using (reader) { }
1 comment
Read more

MySQL Stored Procedure Error

In our project we had many many stored procedures and many parameters passes to those sps. But in only one sp it gives error message something like this; "Incorrect number of arguments for PROCEDURE sproc_t_l_Contract_Select_BySearchCriteria; expected 3, got 2” Work long time on this sp but coudnt find it. So i tried to write it again from the begining. In this time it was work perfectly.This problem occurs because of the space between data type and its length. Ex. pName varchar(50) - working pName varchar (50) - Not working But it does not mention syntax error or something.So this error message make us vulnerable.
1 comment
Read more