WHAT IS "GOOD TASTE" IN SOFTWARE ENGINEERING?

Summary from the TLDR newsletter

Taste is the ability to adopt the set of engineering values that fit the current project. It's different from skill - it's possible to be technically strong but have bad taste or be technically weak with good taste. Almost every decision in software engineering is a tradeoff. Often, you have to make tradeoffs between engineering values, such as resiliency, speed, readability, correctness, and flexibility, and that's where taste comes in. Bad taste is when your preferred values are not a good fit for the project.