> The job was never to type the code out. The job was always to take a problem in the real world, and shape it into a model which can be implemented in software.

"Typing" the code was never the whole job, and it can be the easiest part. But "the code" is very much the artifact that is used to generate values. It being correct and easy to maintain lower the associated costs and MAY raise its value. It being brittle and hard to maintain raise the associated costs and WILL lower its value.

So being good at system design is how you target the first case.