this is a very insightful article! i have worked quite a bit with bpms'es, apache camel and such and experienced the inflexibility, brittleness myself..

so any larger application can become very easily 'overengineered' and of less value to the bricoleur.

there are some good examples of bricolage systems mentioned here, like unix shell commands etc.

but in a more application design-specific context targeted to 'normal' (non-technical) users i was wondering if flow-based programming (e.g. noflojs.org) could offer a better balance between well-engineered small (maybe even tiny) building blocks and bricolaging them based on personal preferences (e.g. visually) to bigger, useful apps.

flow-based programming had a good uptake initially, but i'm not hearing much about it of late..

any opinions or experiences?