Too often, you won’t be given time to make your software understandable. Probably almost never. So you have to incorporate a way of programming that leaves your code more understandable after you fixed your bug or added your feature.
I don’t know if understandability is the most important thing. However I certainly agree with the author that it’s curcial, if you ever want to do more than merley a script or a proof of concept.
Too often, you won’t be given time to make your software understandable. Probably almost never. So you have to incorporate a way of programming that leaves your code more understandable after you fixed your bug or added your feature.
I don’t know if understandability is the most important thing. However I certainly agree with the author that it’s curcial, if you ever want to do more than merley a script or a proof of concept.
So write it properly from the get-go. You can get 90% of the way by naming things properly and following the Single Responsibility Principle.