In some ways, this has always been good programming design. Have clean interfaces. Encapsulate state, and have clear propagation of state between components. Id

In some ways, this has always been good programming design. Have clean interfaces. Encapsulate state, and have clear propagation of state between components. Identify appropriate abstractions that represent the components of your system such that they can be composed, potentially reused, and can be clearly reasoned about and tested. Pulling this into the explicit programming framework rather than just being a set of good design patterns does seem like it help when collaborating with semi-trusted participants. This is how most "low-code" systems work.