3 ms·
It can be useful criticism or an indicator where you could move towards in the future, but for the current project it won't help you. This kind of criticism is
by atoav 7y ago
It can be useful criticism or an indicator where you could move towards in the future, but for the current project it won't help you.
This kind of criticism is even less useful if you are doing e.g. music. Let's say you are part of a Death Metal band and ask for criticism on your music because you want to get better as a band.
The most useful (negative) critic will be a friend who has been listening to Death Metal for years, plays it themselves, has a open mind about different genres, knows what you're after and still will give you the straight hard truth.
The least useful negative critics will be the ones who say they don't like metal and think your music is too aggressive or the metalhead who wants you to do another subgenre of metal because they like that more.
Music of course is more based on taste and subjectivity than software development should be, but one can transfer at least some of this idea: people will often argue from the perspective of their preferences, completely ignoring the scope and goals you publicly stated. And if your goals as a software developer don't align with your critics preferences, their criticism can lead you astray without you noticing it.
It can still be calid in terms of redefining your scope or expanding your goals, but it doesn't help you to get better within them.
Good negative criticism takes seriously what you wanted to do (if it makes sense!) and jelps you to get better at that.