1. 6
  1.  

  2. 2

    I was thinking about the idea of batching, because it seems the trend is often the opposite. Wizards with a dozen screens to work through. Sometimes recommended as best practice because it doesn’t overwhelm the user. That’d be analogous to a function with 20 arguments, which is better broken up into several calls to more manageable functions.

    1. 2

      It’s the same with APIs. You can have a specialized endpoint/facade that aggregates a lot of different data, or micro-services/serverless cloud functions that only do one thing.