@BNZ please fix the credit card checkout flow for business credit cards. Your BNZ for business app does not support the approval flow and it causes serious friction. cc @WindcavePayment@HELLpizza666
@FlyAirNZ No wonder you're struggling. Trying to book tickets at https://t.co/5TW1a7iUf9. Fails twice, jacks price up $200 and kicks me to the call center. On hold for an hour so far, no indication except "we're busy". Either invest in your call centre, or fix your web experience
@benjchristensen was your talk "Don't build a distributed monolith" taken down at your request? And/or are you able to make a copy available publicly? It has been a vast source of inspiration and I'd love to keep sharing it.
@CoverallsApp Can you please explain the best way to get in touch with your support? Your website and twitter point to [email protected] but I repeatedly get this message.
Here's our 3 step guide to accessing the free radio commentary on #RWC2019
1. Tap 'Listen Live' 👉
2. Select your preferred language 🇬🇧🇪🇸🇫🇷🇯🇵
3. Click Play on the TuneIn Player 📻
#RWCRADIO@WorldRugby@rugbyworldcup
@normankev141@andy__carrell@pusher 4/4 return types (BufferedEvents) this is shouldn’t be removed and instead become a documented dead piece. Neither of these are particularly nice but better that breaking 100(00?)s of builds. Another reminder of why considered API design is so important up front!
@normankev141@andy__carrell@pusher 3/4 failing the linter isn’t nice, when you have a substantial number of users consuming that lib, the niceness of the breaking change has to be weighed against the time of each consumer fixing their build to accommodate the change. Furthermore when you end up with redundant
@normankev141@andy__carrell@pusher 2/4 are using which client libs and therefore who you should warn about the changes. In general my thoughts are that you should avoid breaking changes as much as possible - especially ones that break builds and are just annoying (.AppId -> .AppID) . While I understand libs
@normankev141@andy__carrell@pusher 1/4 Hi Kevin, thanks for replying. Apologies for the sarcasm, it was born of frustration but still glib. Im not sure if you had a deprecation warning for these changes, but they didn’t reach my registered email. I imagine you have capability in your systems to see which accounts