I wouldn't go about fixing the messages/symptoms, but after "software engineers" doing things wrong.<p>Also if it's really "always" one might consider the option that one goes about things the wrong way, and especially not implying that someone is mean spirited as the phrase "you are not good enough" seems to imply.<p>It could also hint at things like thinking software engineering is about quickly copy pasting stuff from Stack Overflow or tutorials and somehow making it "run", which at least isn't the only way to go about software engineering and in my opinion certainly isn't the best.<p>Given that the trend is to essentially create more of these (see Rust, Typescript, hinters, linters, etc.) to create better software I think more feedback is the way to go, because then one doesn't end up being scared that things will go wrong at the worst time.<p>As a software engineer I think feedback should be embraced, especially when it is direct, because it makes it more helpful than some vague "it's down", "feature X doesn't work".<p>I also don't think it's good to complain about neutral feedback, because the idea of "nice" error messages sounds scary, annoying and like it a waste of valuable time that people in general tend to have too little of. I'd rather spend that time NOT dealing with an error.