Software quality beats delivery speed for most developers
-
The latest State of Software Quality survey from continuous reliability company OverOps shows that 70 percent of respondents say quality is paramount and they would rather delay the product roadmap than risk a critical error impacting their users.
So that's 30% of developers I don't want to work with
Although it does explain a lot of recent news items
-
The latest State of Software Quality survey from continuous reliability company OverOps shows that 70 percent of respondents say quality is paramount and they would rather delay the product roadmap than risk a critical error impacting their users.
So that's 30% of developers I don't want to work with
Although it does explain a lot of recent news items
Kent Sharkey wrote:
So that's 30% of developers I don't want to work with Although it does explain a lot of recent news items
I was having more the impression that those 2 statistics are the other way around.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
The latest State of Software Quality survey from continuous reliability company OverOps shows that 70 percent of respondents say quality is paramount and they would rather delay the product roadmap than risk a critical error impacting their users.
So that's 30% of developers I don't want to work with
Although it does explain a lot of recent news items
On the serious side: Too many academic style developers have no idea about what the customer really needs. They insist on absolutely everything being toally perfect according to every academic principle ever thought up. The customer cries for "something that solves my problem - now!", but the academic developer says "We are not going to give you that even if we could, because that solution will lack perfectness according to some academic disciplines!" I have worked with some developers of that class. And argued with a lot of that class. What made IBM more or less supreme in some markets in the 1960s-70s is not that they provided perfect solutions, but provided solutions that were good enough, and that with a reasonable margin. Microsoft has repeated that: They have, in a number of market segments, been big for the last 20-30 years not because they are perfect, but good enough (once more: with a reasonable margin). A major part of the critisism against MS (as it was against IBM) is that they are far from perfect. Which is true. By some criteria, Linux is closer to the perfect ... but unable to provide to the non-programmer user what solves his problem now (that is, without having to wait for some other successful windows application to clone). Don't let the best block the road for the good. But we too often do. We do not listen to what the customers really need but let our own ideas of perfection stand in the way of what would solve the user's problem. To say it bluntly: Having to restart your machine is a far more essential problem to developers than to users! (I restart my car whenever I manage to kill the engine. As long as no expert car driver is sitting in the passenger seat shaking his head, it doesn't bother me to turn the ignition key for half a second. .. I have a somewhat problematic driveway for backing up into.)
-
The latest State of Software Quality survey from continuous reliability company OverOps shows that 70 percent of respondents say quality is paramount and they would rather delay the product roadmap than risk a critical error impacting their users.
So that's 30% of developers I don't want to work with
Although it does explain a lot of recent news items
Most managers don't, so doesn't matter much what devs want. Security is a non-issue nor is quality when compared to meeting the deadline and the promises of sales. We want to deliver secure and tested. Much software in the wild isn't. Don't blame us. And stop wasting money on "studies" for the why; it is a budget/time issue, and most of them prefer sub-standard results, and they get those, as deserved.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
On the serious side: Too many academic style developers have no idea about what the customer really needs. They insist on absolutely everything being toally perfect according to every academic principle ever thought up. The customer cries for "something that solves my problem - now!", but the academic developer says "We are not going to give you that even if we could, because that solution will lack perfectness according to some academic disciplines!" I have worked with some developers of that class. And argued with a lot of that class. What made IBM more or less supreme in some markets in the 1960s-70s is not that they provided perfect solutions, but provided solutions that were good enough, and that with a reasonable margin. Microsoft has repeated that: They have, in a number of market segments, been big for the last 20-30 years not because they are perfect, but good enough (once more: with a reasonable margin). A major part of the critisism against MS (as it was against IBM) is that they are far from perfect. Which is true. By some criteria, Linux is closer to the perfect ... but unable to provide to the non-programmer user what solves his problem now (that is, without having to wait for some other successful windows application to clone). Don't let the best block the road for the good. But we too often do. We do not listen to what the customers really need but let our own ideas of perfection stand in the way of what would solve the user's problem. To say it bluntly: Having to restart your machine is a far more essential problem to developers than to users! (I restart my car whenever I manage to kill the engine. As long as no expert car driver is sitting in the passenger seat shaking his head, it doesn't bother me to turn the ignition key for half a second. .. I have a somewhat problematic driveway for backing up into.)
Member 7989122 wrote:
Microsoft has had repeated that:
I give you Windows 10 is not really that bad (ignoring the messy updates) but current Microsoft is far behind from what it was.
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
The latest State of Software Quality survey from continuous reliability company OverOps shows that 70 percent of respondents say quality is paramount and they would rather delay the product roadmap than risk a critical error impacting their users.
So that's 30% of developers I don't want to work with
Although it does explain a lot of recent news items
It's a 30\70 split for managers too....
-
The latest State of Software Quality survey from continuous reliability company OverOps shows that 70 percent of respondents say quality is paramount and they would rather delay the product roadmap than risk a critical error impacting their users.
So that's 30% of developers I don't want to work with
Although it does explain a lot of recent news items
And yet most of us manage to deliver low quality software late....
-
The latest State of Software Quality survey from continuous reliability company OverOps shows that 70 percent of respondents say quality is paramount and they would rather delay the product roadmap than risk a critical error impacting their users.
So that's 30% of developers I don't want to work with
Although it does explain a lot of recent news items
How can I get my manager to read this, and actually believe it? I've been trying to get him to understand quality over quantity for a long time. But his priority is all about pleasing the people at the top.
"...JavaScript could teach Dyson how to suck." -- Nagy Vilmos