The question can be split into the user experience for developers vs the business parts of the process. I don’t think the 2 can be entirely divorced while thinking of what makes software good. Good engineers would want their software to be well crafted but it’s always a trade off between how you’re delivering value to business by making it work right for your users vs making it right for developers. A good software strikes a balance between the 2 in a way the delivers business value while not killing developer productivity in the long run.
Then there are aspects that are related to code. In those terms code that is consistent (follows team agreed definitions on naming conventions, code formatting, styling etc), APIs that are guaranteed with well written tests so that developers can develop with confidence, has good infrastructure for common idioms such that the developers mental burden is taken off of the how to do and focused on what to do are the things that come to my mind.
Comments
The question can be split into the user experience for developers vs the business parts of the process. I don’t think the 2 can be entirely divorced while thinking of what makes software good. Good engineers would want their software to be well crafted but it’s always a trade off between how you’re delivering value to business by making it work right for your users vs making it right for developers. A good software strikes a balance between the 2 in a way the delivers business value while not killing developer productivity in the long run.
Then there are aspects that are related to code. In those terms code that is consistent (follows team agreed definitions on naming conventions, code formatting, styling etc), APIs that are guaranteed with well written tests so that developers can develop with confidence, has good infrastructure for common idioms such that the developers mental burden is taken off of the how to do and focused on what to do are the things that come to my mind.