Anti-patterns and Malpractices in Modern Software Development (2015)

Re:Anti-patterns and Malpractices in Modern Software Develop... by mojuba on Monday October 24, 2016 @01:21PM (#12780805)

The tragedy is that, with non-critical software that can't kill anyone, users are happy with most bugs most of the time. Therefore we will never have legal quality standards for most types of software.

[ Parent | on HN ]

Re:Anti-patterns and Malpractices in Modern Software Develop... by ghurtado on Monday October 24, 2016 @01:38PM (#12780978)

I realize that you're talking about "quality standards", but depending on the industry, there are plenty of legally mandated software standards out there. You're likely to run into some of them if you haven't already:

- 508 / ADA compliance

- HIPAA

- AICC / SCORM / cmi5

- PCI / DSS

[ Parent | on HN ]

Re:Anti-patterns and Malpractices in Modern Software Develop... by 0xdeadbeefbabe on Monday October 24, 2016 @01:51PM (#12781088)

Some of those are not very good i.e. not quality standards. Is there a quality standard for quality standards or does the buck stop there?

[ Parent | on HN ]

Re:Anti-patterns and Malpractices in Modern Software Develop... by ghurtado on Monday October 24, 2016 @02:13PM (#12781281)

Well, that's just the thing. Whether (we) programmers like it or not, the only relevant measure of quality in a program is whether it does the thing that the user needs it to do. In other words, "functional standards" is the only type of quality standards that you could ever expect to have for software.

Things like code quality and inner loop optimization are largely irrelevant for the people who are using the software.

[ Parent | on HN ]