It's closer to a craftmanship kind of care. Being proud of what you're putting into the world. Caring that it works well, not because the purpose is important, but because it's something you're doing and you want to do it well.
It's closer to a craftmanship kind of care. Being proud of what you're putting into the world. Caring that it works well, not because the purpose is important, but because it's something you're doing and you want to do it well.
But it is management's job to decide on software quality standards and provide feedback to devs. Expecting the developers to be responsible for quality as a baseline is just a path to burnout for those devs; because then they are going to go mad because everyone on the team has different personal standards. The person with the highest standards on the team will never be satisfied.
You can't reasonably expect teammates to cover for bad managers, it is much cleverer to learn to identify good managers and try to work for them. Or become one.