Chapter 16

I like the part when Aristotle told Mr. Tompkins that he had a manager that started to do his job by fear this is bad because as I said in some chapters before a manager that use fear to motivate people is not a very good manager, this because people perform worse in a state of fear instead of making them feel part of a team where their contribution is important and that feeling makes people feel good about themselves.

So using fear or contempt to motivate the employees is a sign that the manager is not good, this because all that causes are negative effects in the team and I agree in the part that if a upper manager motivate their people by fear then another lower manager is going to copy that style of managing the project an so on, so as we saw in the last chapter just by making people feel fear and pressure that does not mean that they are going to think and do their jobs faster.

Moving on in the part they started to talk about the spec documentation it was very interesting how in a professional project somethings that happen in school can appear, that specification documents that didn’t say anything about the project were the product of individual shame, it had happened to me in the school that I wrote some complex code and part of my team instead of asking me what I was doing in that part of the code or why a made that part in that way, they don’t ask because of shame and then I realised that part of the code was wrong. So in the case of the novel it happened something similar, the documentation that said all the specifications for that big project of million of dollars was all wrong because it didn’t fulfill its duty and professionals were ashamed of making questions about the document thinking that they were the ones that were in fault.

So in conclusion I consider important that all the documentation in the case of programming is as clear as possible and to prevent that is important to solve all the conflicts they are present in the project so in this way you can have all clear and understood before actually making a documentation about the specs of a project, because without a good specification document you would have a really bad time doing that project.