Yahoo’s engineers move to coding without a net
-
What happens when you take away the quality assurance team in a software development operation? Fewer, not more errors, along with a vastly quicker development cycle.
Ignoring the obvious comment about Yahoo's strength as a company these days
-
What happens when you take away the quality assurance team in a software development operation? Fewer, not more errors, along with a vastly quicker development cycle.
Ignoring the obvious comment about Yahoo's strength as a company these days
-
What happens when you take away the quality assurance team in a software development operation? Fewer, not more errors, along with a vastly quicker development cycle.
Ignoring the obvious comment about Yahoo's strength as a company these days
I'd like to know how this works in practice. As we all know, developers shouldn't test their own code, so who exactly is testing the code if not a tester? Even if they are writing all sorts of automated tests and creating tools, are they still testing their own code? If so, then I don't see how this could ever be a successful strategy. It smacks more of cost-cutting measures than a genuine desire to increase quality.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
What happens when you take away the quality assurance team in a software development operation? Fewer, not more errors, along with a vastly quicker development cycle.
Ignoring the obvious comment about Yahoo's strength as a company these days
I've noticed this trend a couple of years ago. Dedicated QA departments are becoming a thing of the past and developers are expected to write automatic tests for their code.
-
What happens when you take away the quality assurance team in a software development operation? Fewer, not more errors, along with a vastly quicker development cycle.
Ignoring the obvious comment about Yahoo's strength as a company these days
Wait...Yahoo! ? Let me think...? That's that company that did the same stuff that altavista.com did, right? Right? Wait, you're ignoring me, aren't you? :laugh:
-
What happens when you take away the quality assurance team in a software development operation? Fewer, not more errors, along with a vastly quicker development cycle.
Ignoring the obvious comment about Yahoo's strength as a company these days
Well, duh! :doh: It's quite obvious you'll find less errors if no one is looking for them!
Wrong is evil and must be defeated. - Jeff Ello
-
What happens when you take away the quality assurance team in a software development operation? Fewer, not more errors, along with a vastly quicker development cycle.
Ignoring the obvious comment about Yahoo's strength as a company these days
We should do this in airplane and car manufacturing as well to make them safer!
Wout
-
Then the end user have to report and life with the bugs. As I - with my Yahoo-Mail :mad::mad::mad:
Press F1 for help or google it. Greetings from Germany
This is a disturbing trend in the name of quicker dev cycles. That's not what we ask for though.
-
I'd like to know how this works in practice. As we all know, developers shouldn't test their own code, so who exactly is testing the code if not a tester? Even if they are writing all sorts of automated tests and creating tools, are they still testing their own code? If so, then I don't see how this could ever be a successful strategy. It smacks more of cost-cutting measures than a genuine desire to increase quality.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
It works by writing unit tests or even better, using test driven development... Anyway what's wrong with testing your own code? - Everybody tests their own code! do you really hand over your code to QA without at least making sure it works? I alway test what I write.
-
It works by writing unit tests or even better, using test driven development... Anyway what's wrong with testing your own code? - Everybody tests their own code! do you really hand over your code to QA without at least making sure it works? I alway test what I write.
Yes of course I test my own code, and write unit tests too. I do all the same things that Yahoo engineers do, but I go one step further and hand my code over to a tester for independent verification. My code may work, but that's not the end of the story. My UI needs to be consistent with the rest of the application and it needs to trigger failures and omissions consistently for example. Having your code tested by an independent testing team gives a level of verification above and beyond what a developer on their own can give.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter