3 ms·
Because we design around database tables and not workflows. Quite often our underlying architecture simple mirrors the database structure with pattern like the
by flukus 10y ago
Because we design around database tables and not workflows.
Quite often our underlying architecture simple mirrors the database structure with pattern like the Repository pattern and Active Record. Then it flows to the user. Instead of the user creating x as part of their workflow, they have to first create x on the "add x" page then go back to what they were doing.
Of course this only applies to some software, you couldn't make a word processor that encapsulate the user workflow, but for many apps, especially LOB apps, you can.