I think I'm a great programmer because I know the difference between 100% correct and 99% correct, and refuse to call something 100% correct when it's not. I t

I think I'm a great programmer because I know the difference between 100% correct and 99% correct, and refuse to call something 100% correct when it's not. I think I'm a great senior developer because I know when to compromise. Notice that I can do both of those things at once without conflict. It's important to understand potential problems with a solution, as well as problems with alternative solutions, and pick one that seems the best at the time. Many people on the internet are unable to do one or the other, and also feel the need to weigh in on a conversation for their own needs. But not everyone weighing in is wrong. When someone says "You should always X", you will inevitably get someone saying that's false because it is false, and it's important to understand when to break the rules.