Polish is Important

Published 📅: ....
Last modified 📝: ....
Location 📍: Flying from BOS to PDX

Share this status update on BlueskySee discussion on Bluesky

I think a key difference that distinguishes between good software and great software is polish. Often that polish can take the form of things that seem invisible to the user yet still make the user experience orders of magnitude better.

Polish in software development can take the form of almost anything, it can mean;

• choosing the 90% correct default for an option automatically
• providing a blazingly fast experience
• reducing the amount of steps to complete an action

generally most of this boils down to anticipating the user's needs and solving for them quickly.

Some common examples that I often want/reach for include:

• offering comprehensive upgrade guides in addition to changelogs
• prefetching high intent links/actions within a website
• providing off ramps when introducing potentially undesired changes (e.g. allowing for credible exit, or supporting previous versions of APIs)

In the same vein as polish being the difference between good and great software, investing effort into polish can be a difference between good and great software engineers.

Tags:

Loading...