I think I understand your point. The fact is that orchestrating tasks in a reliable way in a distributed environment is a complex task even for skilled software engineers. For them, a "workflow as code" approach is relevant as it avoids a lot of boilerplate code. As pointed out in the conclusion, it can be used also to code "true" DSL of even no-code solutions for non-(or less) technical people