Marco Silva keeps a short list of approved patterns and a longer list of retired ones.
He says taste is enforced when the golden path is also the easiest path.
His guide includes error copy, naming rules, and when to say no to a custom cluster.
Platform engineers shape culture by what they make frictionless.
Taste is not softness — it is opinionated infrastructure.
Marco’s guide to taste began as a list of things he was tired of reviewing.
Custom clusters for ordinary workloads. Error messages that blamed users. Service names only the original developer understood. Dashboards with no owner. Secrets passed through tickets. Every exception looked small. Together they made the platform feel noisy.
He started writing down approved patterns, but the important part was not the list. It was the reason behind each default. This pattern is easier to support. This naming rule helps incidents. This error copy respects the business user. This template includes observability because nobody remembers it under pressure.
Taste, in Marco’s world, is not decoration. It is the discipline of making the right thing easier than the messy thing.
One product team wanted a custom deployment path for a campaign. The request sounded urgent. Marco asked what made the workload special. After one hour, they discovered the standard pattern worked if two small defaults changed. The team shipped faster because the platform said no to unnecessary uniqueness.
His longer retired-pattern list became more educational than the approved list. It showed the organization what it had learned: which shortcuts caused incidents, which designs created ownership gaps, which clever ideas became maintenance debt.
Platform taste is felt by other builders. It lowers the number of decisions they have to make before doing useful work. In fashion, where deadlines already create enough pressure, that kind of taste is a quiet gift.
