• Home
  • Blog
  • Projects
  • Bookshelf
  • About
← Back to all status updates

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:

micropostSoftware Development

Bluesky Post and Comments:

Loading comments...

Related Posts

micropost

<Blank> Driven Development

Published: ....

All Documentation Should Be Dated

Published: ....

Adding Microposts

Published: ....

Service Monitors and Observability

Published: ....

Leveraging service monitors properly to improve service observability.

Being Unopinionated

Published: ....

It's fine for a library to express some opinions about how it should be adopted and how the overall workflow/application in which it is adopted should function. However, it's false advertising to say that it is unopinionated.

Stop Snacking

Published: ....

No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).

No Process is Invisible Process

Published: ....

Low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.

Software Development

You're Building Software Wrong

Published: ....

Slicing software: why vertical is better than horizontal.

Matt Hamlin

Matt Hamlin

@matthamlin.me

New micropost: Polish is Important

matthamlin.me/2025/june/po...
Polish is Important

Polish is Important

https://matthamlin.me/2025/june/polish-is-important
3 days agoView on bsky.app
0
0
0
0