An interesting analogy. But note that movie output is a fixed blob with NO degrees of freedom, makers have fewer combinatorial problems, and staffing according

An interesting analogy. But note that movie output is a fixed blob with NO degrees of freedom, makers have fewer combinatorial problems, and staffing according to a well-defined set of fixed roles with little or no pressure to change that. In contrast, the output of a software project is an interactive machine with enormous degrees of freedom, makers deal with 3 OOM more combinatorial problems (by dint of logical dependencies changing 1000x faster than physical ones), and staffing roles are ALWAYS subject to change with enormous pressure to "innovate" those roles, particularly by smushing them together (e.g. full-stack, devops roles, the end of sysadmins and db admins). What you suggest may be possible within a large and static consultancy that fixes the roles and dependencies for 5-10 years at a time, but such a firm might have a tough sell. Even success stories like 37signals who've been using the same language consistently over its 25 years probably could not do what you suggest.