3 ms·
While I appreciate the intent of your article, I think the title is regrettable and obscures the real distinction you were going for. There should never be a di
by davesims 15y ago
While I appreciate the intent of your article, I think the title is regrettable and obscures the real distinction you were going for. There should never be a distinction between "good code" and "good software."
The Software Craftsmanship movement has been having this discussion for a while, i.e., assessing the costs of bad code and making those costs visible to the stakeholders. You might find it worthwhile to engage that conversation.
http://scmanifesto.heroku.com/main http://scmanifesto.heroku.com/main
- danek 15y agoI think the issue is many engineers value things like tests, short functions, interfaces, dependency injection, pure functions, comments, DRY, etc. To them, these things are qualities of "good code", and they spend all their time on this stuff instead of the bigger picture objectives. When you get out of that mindset, then I think "good code" can be equal to "good software".