A client you can still use when you configured it wrong
Go says a constructor either works or it doesn't. That contract stops making sense the moment a client has a dozen optional parts, so I broke it on purpose.
Tags
4 pages
Api-Design
Posting unifies, tokens don't
One interface posts a reel to four platforms cleanly. Their OAuth token handling refused to unify at all, which is why I built all four first.
Two API decisions that quietly contradict each other
A Rust gotcha: non_exhaustive promises an enum can grow, but returning a fixed-size array bakes today count into the type. Both cannot be true.
One variadic, and I'd already spent it
Go allows only one trailing variadic parameter, so adding another argument to a function that already has one is impossible. What to do instead.
