> These are all artefacts of software development as we practice it, rather than truisms. Well, they're not laws of nature or anything. But pragmatically, how

> These are all artefacts of software development as we practice it, rather than truisms. Well, they're not laws of nature or anything. But pragmatically, how could it be otherwise? When it comes to bridges and buildings, correctness beats timeliness, but when it comes to software the opposite is usually true. There are exceptions of course (e.g. medical software) > Maybe we should reserve the term software engineering for the applications of software development where rigour is involved? Agree.