3 ms·
Wow, thanks for that quote. When I worked at Azure, one of the things I was responsible for was the "deep link" code to get to the management page for a resour
by breck 2y ago
Wow, thanks for that quote.
When I worked at Azure, one of the things I was responsible for was the "deep link" code to get to the management page for a resource.
So I became intimately familiar with Azure "resource ids". I could not for the life of me figure out why they were designed the way they were designed. They should have just been a random or custom alphanumeric hash/permalink. I asked my questions and raised my concerns internally but failed to get things fixed (politics is not my strong suit).
My most probable explanation for them was that they were designed by a mole Jeff Bezos had gotten into the Azure org to work on behalf of AWS.
- gradus_ad 2y agoIncompetence does a fine job of explaining this, no?
- SigmundA 2y agoYes Hanlon's Razor is sort of the opposite side of the coin here, almost like Clarks Third law except: "Any sufficiently bureaucratic system is indistinguishable from a cabal of enemies"
- throwup238 2y agoMicrosoft’s signature Incompetence™ Enterprise Edition no less. Overcomplicating things the enterprise way is exactly what I expect from them.
- NoMoreNicksLeft 2y ago> My most probable explanation for them was that they were designed by a mole Jeff Bezos had gotten into the Azure org to work on behalf of AWS. I've read this five times now, and each time I read it I flip on whether it's a joke or some kind of (semi-)anonymous tip being leaked to a journalist through a pre-arranged drop site.
- katbyte 2y agofwiw i am a fan of azure resource IDs as they make it easy to identify what and where a resource is vs a random magic string you have to go look up
- breck 2y agoI think this could be accommodated with changeable permalinks. I understand your perspective. Thanks for sharing.