TL;DR: They fired the QA team to save money. Then they made the engineers do the QA work for no extra pay.
I mean, they have a salary, so unless the engineers are required to stay extra hours to do the QA it makes no difference to them.
Yahoo’s Engineers Move to Coding Without a QA Team
11–20 of 188 posts
Re: Yahoo’s Engineers Move to Coding Without a QA Team
#12They removed only MANUAL QA testing. There is a big difference between removing the QA team entirely and automating QA work.
Re: Yahoo’s Engineers Move to Coding Without a QA Team
#13This will end well.
Re: Yahoo’s Engineers Move to Coding Without a QA Team
#14If this is working so well, why is there still no version of Yahoo Messenger—a core product—for either Mac OS X or iOS?
It looks like Yahoo Messenger for iOS was released on December 3: https://itunes.apple.com/us/app/yahoo-messenger-chat-share/i...
And apparently there's a native OS X client coming, as well: http://mashable.com/2015/12/03/yahoo-messenger-is-back/
Re: Yahoo’s Engineers Move to Coding Without a QA Team
#15That is kind of like having an open kitchen policy (or a kitchen visible via a glass wall) in a restaurant.
Re: Yahoo’s Engineers Move to Coding Without a QA Team
#16TL;DR: They fired the QA team to save money. Then they made the engineers do the QA work for no extra pay.
I think that is a slightly harsh assessment. They forced the engineers to stop shipping shoddy code, so the QA team wasn't necessary in their opinion. However I think there is probably a middle ground where your engineers deliver quality code and you also have a QA team to increase that quality even further.
A failing company cutting QA teams is nothing but a desperate attempt to save money. Yahoo's margins are falling and it's easier to fire people than it is to raise revenue.
Re: Yahoo’s Engineers Move to Coding Without a QA Team
#17If this is working so well, why is there still no version of Yahoo Messenger—a core product—for either Mac OS X or iOS?
Yahoo Messenger for iOS:
https://appsto.re/us/DOV0-.i
Re: Yahoo’s Engineers Move to Coding Without a QA Team
#18TL;DR: They fired the QA team to save money. Then they made the engineers do the QA work for no extra pay.
I think that is a slightly harsh assessment. They forced the engineers to stop shipping shoddy code, so the QA team wasn't necessary in their opinion. However I think there is probably a middle ground where your engineers deliver quality code and you also have a QA team to increase that quality even further.
> so the QA team wasn't necessary in their opinion.
I don't know of any large, complex systems where QA is not necessary. Technology is only fallible because humans are.
Re: Yahoo’s Engineers Move to Coding Without a QA Team
#19TL;DR: They fired the QA team to save money. Then they made the engineers do the QA work for no extra pay.
I mean, they have a salary, so unless the engineers are required to stay extra hours to do the QA it makes no difference to them.
They might as well take out the trash and clean the floors on their way out. Vertically integrated!
Re: Yahoo’s Engineers Move to Coding Without a QA Team
#20This is actually a story about the triumph of continuous integration and staged rollout.
By shipping code constantly, but slowly rolling it out to users - bugs can be detected very quickly by the users themselves, instead of employing large QA teams.
Keeping a central code repository, automating builds, frequent commits and automatic tests for code are taking away a lot of load for QA teams.