Build systems are workflow engines. Workflow engines fundamentally separate and structure code and execution in discrete steps with a graph visualizer (hopeful

Build systems are workflow engines. Workflow engines fundamentally separate and structure code and execution in discrete steps with a graph visualizer (hopefully the graph is acyclical). Maybe it's just a bad example, but the code I saw looked very very unseparated. I understand most people who do builds want start out with the one build file to rule them all model. But ultimately you are dealing with a workflow execution. If you were doing anything aside the most trivial single library build. Next generation of whatever build needs to have the visualization and visualized execution assets. There's a great many things that workflow engines fundamentally applied to. Unfortunately they have been politically associated with management trying to replace developer labor, usually because of the snake oil salesman, the workflow engine people are selling to the the c-suite people. A good common visualization and execution set that's cross language would have been really helpful in so many computing domains. It's almost like we need the SQL of workflow engines to be invented