SOFTWARE VERSION SYSTEM


Every software we use daily has software version and we should also give version number to software we develop everyday.

The simplest one is Semantic Versioning.(http://semver.org/)

Give software version no in form of MAJOR.MINOR.PATCH

  1. MAJOR: Increment it on every major  release
  2. MINOR: increment it on every new feature introduction
  3. PATCH: increment it in every bug fixes or small changes

Here is one example :

  • When you start developing any software give it 0.0.1
  • when you introduce any new feature/module  change number to 0.1.0
  • when you add another module change number ot 0.2.0
  • When you made some changes/bug fixes change version to 0.2.1
  • Once software is ready for publish give it number 1.0.0

Query: When should I change software version number?
Answer: Every time you commit the code you should increment it.(obviously you should use source control systems)

Query: Where can I store it?
Answer: Put it anywhere in project. as Constant in code or version.txt or version.xml or version.json as you like

How to differentiate good code vs bad code


To differentiate between good code and bad code you must have basic knowledge of programming. If you don’t have it the following is list of things you should read about.

  1. Variable
  2. Function
  3. Class and Object
  4. Loops

Once you have idea what they are you need to check for following:

  1. Are name used for variables, functions and classes describes what they contain or how they work? If answer is yes, the code is good.
  2. is code formatting is quite consistent? If answer is yes, the code is good.
  3. is there commented code? If answer is yes, the code is bad.
  4. is file names are meaningful and folder name describes what it contains? If answer is yes, the code is good.

Above are very basic checks if you would like to differential with more details you should read programming best practice books and should learn programming language.