4 ms·

I've been experimenting with what one may call "CRUD shorthand", which is a way to define typical CRUD activities in as short a way as possible. However, change

by tabtab 9y ago

I've been experimenting with what one may call "CRUD shorthand", which is a way to define typical CRUD activities in as short a way as possible. However, changes in UI/UX expectations and/or fads generally muck up the consistency. The industry keeps reinventing the wheel such that we can't stop to master and simplify one kind of wheel: we throw it out for the Next Great Wheel and invent different ways to do the same CRUD things. Some changes are good, others are a waste and distraction. People do judge books by covers, and that costs us. Another "problem" is that software tries to model the messy "organic" external and internal office politics, making the software messy. Either make the organization more logical, or accept messy software that tries to mirror messy human and organization relations.

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 ago
  I 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 ago
    Workflow 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

by tabtab 9y ago

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 ago
I 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 ago
  Workflow 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