Help! I like this excerpt from CryptoPotato's "10 keys for evaluating Initial Coin Offering (ICO) investments" but want to turn it into a series of questions. Anyone able to assist?
Source: https://cryptopotato.com/10-keys-evaluating-initial-coin-offering-ico-investments/
9 Quality of the code Meet Githhub
If you have a little bit of programming experience, you should be using it here. The quality of a developer can be understood by analyzing some of their code. As a non-techie, it is still possible to evaluate their quality by looking at the consistency of the code. Another good indicator, is the usage of proper commenting. Avoid messy developers. A piece of code reflects the attitude of a developer.
Next, the length of a function is another indicator. A function containing more than 50 lines of code should raise a red flag. Modularity is important and makes the code more readable and maintainable.
Crypto projects tend to have open-source code. This creates trust among the projects community, encouraging devs from the community to make suggestions or improvements. An open-source project provides the opportunity to look at the commit logs. A commit is essentially developer slang for pushing a piece of code to the Github code repository.
Thanks in advance,
Crypto-Kristen
Source: https://cryptopotato.com/10-keys-evaluating-initial-coin-offering-ico-investments/
9 Quality of the code Meet Githhub
If you have a little bit of programming experience, you should be using it here. The quality of a developer can be understood by analyzing some of their code. As a non-techie, it is still possible to evaluate their quality by looking at the consistency of the code. Another good indicator, is the usage of proper commenting. Avoid messy developers. A piece of code reflects the attitude of a developer.
Next, the length of a function is another indicator. A function containing more than 50 lines of code should raise a red flag. Modularity is important and makes the code more readable and maintainable.
Crypto projects tend to have open-source code. This creates trust among the projects community, encouraging devs from the community to make suggestions or improvements. An open-source project provides the opportunity to look at the commit logs. A commit is essentially developer slang for pushing a piece of code to the Github code repository.
Thanks in advance,
Crypto-Kristen
And regarding the questions, how about (in order of importance - 1. most, 4. least):
1. Does the code have commentary?
2. Does the commentary explain clearly the purpose of the function?
3. Are the functions a reasonable length? i.e. are they less than 50 lines?
4. How frequent are commit logs? - I would personally leave this one out however. There's an excellent comment in the article left by someone explaining why commits aren't necessarily all that important (if I recall from memory correctly, don't have it to hand atm).