Main rules of criticism in any team: - Constructiveness - criticism should be constructive, i.e. it should offer specific recommendations and improvements. - Specificity - criticism should be specific, i.e. it should point out specific problems rather than generalize about the entire application. - Objectivity - criticism should be objective, i.e. it should not be based on personal biases or emotions. - Usefulness - criticism should be useful, i.e. it should help improve the product. - Tone - criticism should be formulated in a respectful tone so as not to offend developers and create a defensive reaction.