> I wonder what the biggest hindrances are for software development to become this way. At least for our application, it's hidden/non-explicit dependencies and

> I wonder what the biggest hindrances are for software development to become this way. At least for our application, it's hidden/non-explicit dependencies and domain knowledge. By hidden dependencies I typically mean that process X has to be done before process Y, or similar. Meaning you sometimes can't just rearrange things. A substantial integration test suite could help, but it's a tradeoff. Though often it be tricky to test, as it could depend on customer systems we don't have internal access to. Domain knowledge is also needed for much of the code. Of course this could be offloaded to a senior, but then those tend to be the limiting factor. For our team, it's been more effective that all the devs have substantial domain knowledge.