Early in my career, I figured that, the code speaks for itself. If it works, it works! Can't argue with that. That's one of the appealing things about working w

Early in my career, I figured that, the code speaks for itself. If it works, it works! Can't argue with that. That's one of the appealing things about working with machines. They're almost never "wrong", it's always something you can fix, do correctly, and ergo, win. Later I learned, yes, a quick solution can be a good solution; but there can be more than one good solution, and in fact, others can be better. More maintainable, less verbose, so clear and simple there are obviously no errors. Abstractions in the right place and the right level. Modeling a business domain that stakeholders understand. In the same way, just telling somebody "the truth" can get the message across. But it makes you the junior engineer of talking to people. As you grow in your career, you learn that there are many ways to communicate with the people around you. And different tones and patterns appeal to different people... or even to the same person at different times, based on mood or context. You can learn (if you care) to work well with these complicated organic machines we call humans. And you can always get better and better at it, even when you already think you're doing the brave thing, the heroic thing, the right thing.