> The fact that we cannot regenerate our code in the same way is a sign that we do not understand it
That just means that requirements have changed over time and the code has to make concessions to cover all the requirements. That's what complicates any software project and that's to keep happening only that now you won't know the codebase.
The same thing is going to happen if you add another abstraction layer. Okay, you don't need to write code. But you are not going to be able to write a spec that controls all edge cases or changing requirements.
In fact, language is more prone to wrong interpretations so this problem is going to be even more noticeable. Yeah, sure, you can write tests and make sure the code is up to spec, but again you will miss some weird edge cases.
I just don't see the advantage in understanding less about the code you maintain. If anything, I want to know more
> The fact that we cannot regenerate our code in the same way is a sign that we do not understand it
That just means that requirements have changed over time and the code has to make concessions to cover all the requirements. That's what complicates any software project and that's to keep happening only that now you won't know the codebase.
The same thing is going to happen if you add another abstraction layer. Okay, you don't need to write code. But you are not going to be able to write a spec that controls all edge cases or changing requirements.
In fact, language is more prone to wrong interpretations so this problem is going to be even more noticeable. Yeah, sure, you can write tests and make sure the code is up to spec, but again you will miss some weird edge cases.
I just don't see the advantage in understanding less about the code you maintain. If anything, I want to know more