Regarding deployment, the Nix Package Manager (https://nixos.org/nix/) is a very clean solution. It is a package manager and build system, that can be used for building and deploying libraries and applications, with maximal sharing of the same binaries on disk and RAM, but also great isolation: every user/environment/application can use the version of libraries it needs, without influencing other users/environments/applications.

This approach https://nixos.org/nix/ joins the benefits of dynamic and static libraries. Applications are ELF files directly referencing the version of the library they want to use. Different versions of the same library can coexists on the same system, also of glibc in case. Containers on the same machine can too use the same repository of applications and shared libraries, with minimum overhead. I don't know how it is usable in production: I only started playing with it, but it is very sound from a theorical point of view.

A study at IBM concludes:

Software projects with the lowest levels of defects had the shortest development schedules and the highest development productivity... software defect removal is actually the most expensive and time-consuming form of work for software (Jones 2000)

In "Code Complete 2", McConnell says:

Microsoft's applications division has found that it takes three hours to find and fix a defect by using code inspection, a one-step technique, and 12 hours to find and fix a defect by using testing, a two-step technique (Moore 1992).

So paradoxically code-inspection could reduce development time of good-enough products.