Balance severety of errors with ease of fix

[psaegert]

Regarding the balancing mentioned in the Feedback #8, we could make a list for prioritizing the problems, perhaps like this:

Problem	Severity	Frequency	Cost to Fix	Score
Missing Knowledge about APIs	7	4	7	4

Where the score is Severity * Frequency / (Cost to Fix). The higher the score, the more we profit from fixing the problem.

What do you guys think? @KushalGaywala @anacarsi