I disagree. Errors are failures. Not just failures in code execution, but also, objectively, shortcomings of the programmer's skill. It's very difficult to deny

I disagree. Errors are failures. Not just failures in code execution, but also, objectively, shortcomings of the programmer's skill. It's very difficult to deny this because there is usually a lot of evidence. However, there is something to be said about accepting one's mistakes and not wasting time dwelling on them; and instead looking at the bigger picture, or at least at something more constructive. Life in general is a lot better once we learn to do that. For the new software engineers that are too frustrated by their constant mistakes, I want to say a few things: 1. You cannot become an experienced software engineer without getting the experience. 2. You cannot become skilled in a programming language or any tech without spending the time to become skilled at it. 3. You were not born entitled to be a good software engineer. As a baby, you were objectively awful in the discipline. As you have progressed to your current level of expertise in software, so will you continue to progress. 4. It is best to not overthink software engineering and just try to do it well. 5. You are the only judge of your failures and successes in life. No one else in the world decides how you feel about them. It is your prerogative to forgive your own mistakes - big and small (like a coding error) - if you so wish. 6. All new software engineers make many mistakes. 7. Likewise, all experts in every field regularly make mistakes. Just the kind of mistakes are different. But it is the human condition to make mistakes. 8. You will probably get to where you're going in the end if you persevere.