On Mon, Oct 31, 2016 at 5:24 PM, Kasey Speakman <[email protected]> wrote:
> There is a danger in focusing on data over use cases. It's not a guarantee > that you make this mistake (I have), but you know you've gone too far with > it when most workflows are Load/Edit/Save (or Create/Save). And the user is > left to know what field to change to have a specific effect in the > system. I've seen this termed as data-centric. Seems okay at first but > after a few years in production this leads to long user training times, > brittle workflows, and high support loads. > What are the alternatives? How would an approach focused on use cases look like? -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
