3 ms·
CRUD alone doesn’t provide much value to an average company, the real value comes from managing and automating the workflow, which is of curse the expensive par
by LoSboccacc 9y ago
CRUD alone doesn’t provide much value to an average company, the real value comes from managing and automating the workflow, which is of curse the expensive part of developing software because it requires full knowledge transfer from a company that likely has never stopped to understand their process to developers that have varying grades of familiarity with the domain
- tabtab 9y agoI generally consider "workflow" as part of CRUD, although there are more literal interpretations of "CRUD". But changing the workflow shouldn't be that hard if the stack/tool has a standard way of configuring & managing workflows and user roles.
- LoSboccacc 9y agoWorkflow is usually so much more than an object state. You might have required documents or a proof of work that go in attach to the state change, some state change roles might be asymmetrical (i.e. only this role can roll back a state transfer) so permission need to be dynamic depending on object states, and then you have good ole transformative batches on top which are squisitely custom. I mean, I know the problem quite a lot, sice one of my many backburner ideas is a workflow centric self service crud builder :D