Comment by corethree
2 years ago
No. theory is very much part of the creation of the bridge. It is not just for verification.
If you read more carefully. What I am saying is that in software engineering, there is no theory. It's all Design. All made up. There's also no verification of the design itself.
> There's no verification of the design itself.
I think this is mostly a philosophical statement, but it certainly has truth to it.
Code reviews / rework tackle mostly the code, but not the fundamental design. However the execution of the code tackles the design as well:
- If the design is wrong, the result is bad, that is detected at the execution phase.
- If the design is suboptimal (hard to maintain or extend, bad cpu load, hard to reuse...), well that is usually not solved. IMO that matches your point.
>I think this is mostly a philosophical statement, but it certainly has truth to it.
It's fact. What theory is there to prove that the following design is the best possible design? What does "best" even mean? We can't verify formally in anyway how good a design is overall.
We can verify, efficiency, we can verify speed, and we can verify correctness. But design? We can't verify that.
How do you prove that a bridge is the 'best' design? What does 'best' mean, for a bridge?
3 replies →