News for hackers. Stuff that matters.
Re:Investigating Higher Quality Software by tribaal on Friday January 16, 2015 @02:26AM (#8897621)
Well, it seems like a relatively surprise-free article...

Write explicit code, write tests, have QA staff and procedures, build what the stakeholders what.

I guess the biggest problem with software quality is not that we don't know how to do it, but that it's expensive.

Re:Investigating Higher Quality Software by cema on Friday January 16, 2015 @04:08AM (#8897856)
Poor software quality is also expensive. I would like to see a study about the balance points and how to achieve them.
Re:Investigating Higher Quality Software by tribaal on Friday January 16, 2015 @04:34AM (#8897946)
Sure, what I meant is most companies will chose cheap-fast over good-fast, in my experience.

Flinging crap out fast is sometimes seen as a valid business model (unfortunately): that crap is only expensive to you if you have to maintain it, but that's not your problem if all you're trying to do is to "exit".

On the other end of the spectrum (like where I work at now for example), we take a lot of effort and time to make sure our code is not crap - but that is an expensive decision both in terms of money and time.

Re:Investigating Higher Quality Software by blrice on Friday January 16, 2015 @07:25AM (#8898404)
This. I think there's a big space between cheap-fast (crap) and good-expensive (or just "good"). In my experience, we seem to be way more toward the crap side of things. I think we can make a correction without going too far the other way. You can make sacrifices for speed that don't always mean crap in the end. I'm willing to sacrifice perfect architecture in order to get something out the door, for instance.
Re:Investigating Higher Quality Software by collyw on Friday January 16, 2015 @04:14AM (#8897874)
Not always.