Coding convention

The objective of everything is memoriless:
1. You still know your code when 10 years after you come back and look at it.
2. You know exactly where to change the stuff


Method Signature is important
3. Common sense (clear when judging the signature itself)
4. Brief (don't put createNewNode, put create Node)
5. General e.g.
Not so good
 private string getNewName(string prefix, string suffix, List<TreeNode> trs, int startNumber)
Good
 private string getNewName(string prefix, string suffix, List<string>  usedName,  int startNumber)


Organization is important, separate when necessary
1. Separate specific from general (hiearchical relationship)
2. Separate task like UI and logic


Naming
1. Use precise name, not first name in your mind like if it is a start number used startNumber, don't use counter
2. Remove redundant node like createNewNode->createNode




Coding
1. Code one function by one function, other leave as stuff and code later
2. Make the correct architecture when start coding, so any additional task you can add later