Treating code as a low-entropy amorphous blob is a quick way to see bridges collapse.

It works for concrete because its tensile and compressive strengths are well known for a given composition, but for high-entropy products like software you pretty much need to also generate a formal proof to have any assurances.

Which, ignoring the production costs and assuming that the proof is in fact correct, is only ever as good as the specification.

If you were looking for a physical analogy for software development, it's closer to growing crystals than pouring concrete.