3 ms·
"User friendly, clickable in the browser, api urls" seems like... a made-up user requirement? Have they nailed their product so well that this is the highest va
by skeeter2020 4y ago
"User friendly, clickable in the browser, api urls" seems like... a made-up user requirement? Have they nailed their product so well that this is the highest value work outstanding? There's some neat technical details in there but to me this is the definition of engineering procrastination.
- ripperdoc 4y agoChoosing ID strategy is one of those early architecture decisions that has to be done upfront and that can give a lot of headache later if the choice was wrong. So I wouldn't call it procrastination if it's made before starting development. To change it later in the process, just for vanity purposes, would certainly be risking wasting time on the wrong thing.
- counttheforks 4y agoHaving IDs that can't be represented cleanly in a hyperlink makes them pretty useless if you're building a web facing service.
- dpkirchner 4y agoIf making the urls easy to copy saves them even a handful of support requests, it's worthwhile.
- nickvanw 4y agoHi! I'm the VP of Engineering at PlanetScale and was at the company when we made this decision. We had the advantage of being able to decide to do this up front when we were first building the current product. The marginal work for this was nearly zero because we did not have to migrate anything existing, we just decided to address our resources using this strategy. In that way, there was nothing procrastinated -we just decided this was a good idea, and did it. I can speak from firsthand experience, however, how useful it is to be able to copy/paste links and references to resources. It makes support, collaboration and work much easier when you can easily share links to resources.