Like other intellectual activities, the task of programming and how people learn to program computers is well studied.

This fact is related to Psychology field research. The results indicate that when a person has a problem he/she does not report complete information about the problem, especially when it is responsible directly or indirectly. This result has been confirmed experimentally with programmers and one of the main reasons is the following: to fully report a problem is seen as a sign of weakness that can lead to some kind of judgment of skill and proficiency by whoever is listening to the story. This situation is more common when it comes to a fundamental error committed by novices.
 The classification of a programmer progress is important to support multiple metrics involved in software development and also help project managers and other professionals to evaluate how good the project is as a whole.

Moreover, it is also important to know in which phase of the progress the developer is to, among other things, offer some kind of help so that he does not spend too much time stuck in a specific task to the point of delaying any deliveries. An interesting classification identified (automatically) four possible states of progress:

a) Complex Programming
 b) Making Progress
 c) Slow Progress
 d) Stuck

Besides the classification of beatable and unbeatable programming barriers there is a very interesting study that feature each of the possible programming barriers. T
b) Selection: “I know what to do, but do not know what to use”.
c) Coordination: “I know what to use, but do not know how to combine what I need”.
d) Usage: “I know what to use, but do not know how to use”.
e) Understanding: “I thought I knew how to use X, but it does not do what I expected”.
f) Information: “I understand what happened, but I can not check”.