My experience attempting to debug a freaking podcast feed reminds me of how far we as an industry need to go with regards to developer experience.
-
-
This is surprising to me, as people who use podcast clients written by companies who can write software continued interacting with the (previously working for years) podcast w/o incident, but maybe there is some fun parsing bug. Finding it is impossible with that error message.
Show this thread -
I then go to their documentation about submitting podcasts and error states, and promptly wished I hadn’t. Their actual suggestion with regards to debugging feeds is to pass them through a 3rd party validator and pray, because they have no first party way to validate.
Show this thread -
(They do, of course; something needed to crawl my feed and try to download episodes. But because it is entirely opaque they hope that other software is broken in exactly the same way theirs is. Sadly, this is not the case.)
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.