> switch

Hmm, that hit a bit of a nerve. My experience with switch blocks is it can be a gateway drug for teams A, B, C to add their special-case code to team D's repo within a `switch(calling_service)` block. My read of the presentation is more, factor your stuff so that any "switch" is a higher level concern that consumers can do in their own services. Then if you start to see all your consumers write very similar consumption logic, then start thinking about how to pull that down into the library/service itself.

But beyond that trigger nerve, agreed.

fair enough. I think switch statement is a broader category for "basic programming primitives that you should just do yourself" -

agree big switch statements can be an anti-pattern, e.g. when an interface is clearly better suited