As I’m slowly evolving my own flavour of spec driven development, I’m starting to think about the generated code as a secondary artefact where main quality criteria is that it’s doing what it needs to and it’s covered with tests.
I guess my current analogy is that I don’t care about how readable or dry is the assembly code generated by compiler.
I have the specifications and the working code with tests. I can always regenerate it if I need to.
But. I still read the produced code, steer the design and correct the obvious blunders. No vibes.
As I’m slowly evolving my own flavour of spec driven development, I’m starting to think about the generated code as a secondary artefact where main quality criteria is that it’s doing what it needs to and it’s covered with tests.
I guess my current analogy is that I don’t care about how readable or dry is the assembly code generated by compiler.
I have the specifications and the working code with tests. I can always regenerate it if I need to.
But. I still read the produced code, steer the design and correct the obvious blunders. No vibes.