4 ms·
> TLDR: Please don't do this: https://company.com/resource/c6b10dd3-1dcf-416c-8ed8-ae561807fcaf https://company.com/resource/c6b10dd3-1dcf-416c-8ed8-ae56180...
by AirMax98 2y ago
> TLDR: Please don't do this: https://company.com/resource/c6b10dd3-1dcf-416c-8ed8-ae561807fcaf https://company.com/resource/c6b10dd3-1dcf-416c-8ed8-ae56180...
But like... why? This article literally does not explain the benefits beyond copying, they are just assumed. I'm not immediately sold on shorter === better, especially when the updated UUIDs are only marginally shorter and you have now introduced the overhead of a translation layer for one of the most basic building blocks in your application.
- mynameisvlad 2y agoI thought it was fairly well reasoned in the article. Let's say you have a customer with that UUID as their ID. Do you expect them to recite their UUID perfectly to you every time? What if they made 5 transactions, each with their own UUIDs and you need to look them up, do you now expect them to read out 6 fairly unwieldy IDs? The article is about the UX of UUIDs. Yes, there's a translation layer and more dev work to implement, but the shorter size and use of non-ambiguous characters is a massive improvement in the usability for the end users.
- eviks 2y agoYou've added an overhead where it had trivial costs and limited to be handled by professionals to reduce an overhead where it's annoying many more people, including poor customers Also, you don't explain why copying isn't good enough, you just reject the article's reasons