Recent searches
Search options
@adamchainz one of my favorite photos of my cats re-enacts this scene
@CodenameTim haha amazing
@adamchainz Even better when it doesn't have versioning
Mehdi.doc @adamchainz you must not go there, or we'll get thousands of complaints on retro compatibility issues
@mehdi_benadel a thousand hyenas laughing as Simba tries to comprehend the labyrinth of code
@adamchainz This is so real.
@adamchainz oh god. felt. my last job literally hired me specifically to lead api v2
@rachaelspooky @adamchainz i am staring at this while requesting comments in my org for an "API v2" draft that i've just written up. ughhhhh.
@dragonminded @rachaelspooky just wait for v3!
@adamchainz I've definitely been part of the problem multiple times in the past. In my defense, it's surprising how many services replace a fully featured API with a far more elegant, better documented one that's missing some critical feature (although I'd be willing to bet most other cases are just people who don't want to figure out authentication with OAuth, and honestly: can't blame 'em).
@gordoooo_z @adamchainz also 95% of the developer documentation is written against v1 as well as 99.99% of code examples elsewhere on the internet.
@tedmielczarek @adamchainz Definitely also true.
@adamchainz *which corporate outsourced to the lowest bidder
This hurt me in a place I didn't know could be hurt
@adamchainz If you would implement the other 75% of the functionality of V1, we might start migrating. Especially if you fix the performance problems in V2.