I disagree on the phrasing. When I'm teaching beginners or juniors in a school or professional environment, as I said, I hammer that it doesn't have to be perfe

I disagree on the phrasing. When I'm teaching beginners or juniors in a school or professional environment, as I said, I hammer that it doesn't have to be perfect. It never will be. Don't over engineer things. But everything NEEDS to be right. Where right means the problem is solved, the code is understandable, the patterns (and there must be a pattern) are easy to discern and emulate. Along with proper code formatting- I am amazed at how many people in the workforce don't even understand how important formatting is! FFS most IDEs will auto format with a keystroke. 'Right' is definitely subjective, so to you, right be what I call perfect and we're talking about the same thing. But I feel like if someone is hearing me say it doesn't have to be right, I'm excusing bad behavior and shit code. Whereas when I say it doesn't have to be perfect I'm saying a small amount of code smell or some tricky areas are acceptable if they can't be helped given the money and time constraints.