http://minimsft.blogspot.com/2006/03/vista-2007-fire-leadership-now.html
so i was reading that. i also work at another large software company and well all our stuff gets pushed back, everything takes 500 hoops to jump through to get done, oh and we have like 5000 program and product managers who have no clue about software and are retarded. granted there are some good ones, and those would probably be the other 2500.
here is one comment:
"
In the last 18 months this org:
1) Cut the number of testers (several times) from approx 50 to now much less than a dozen. Of course, many top performers also left MS entirely because of middle mgmt in this org.
2) Hired more PMs
3) Cut the scope of testing (anyone done any real code coverage testing lately?)
4) Cut the number of promotions in the test orgs - nothing like a little 'de-incentivization' to increase 'bad attrition'
5) Dictate that everything can and should be automated. (Ignore that eyeballs catch more in less time...) way to go Darren. Of course, you were probably lied to by your underlings, so it's not entirely your fault. Uhh, yes it is - you made the call.
6) Hire only a small handful of devs to write automation code. Oh, and don't forget to swamp them with added process and have embittered leads review their code...
7) Hire more PMs
8) Outsource all testing to non-accountable and barely trained CSG firms overseas (Ever try to translate/clarify a bug written not by a tester, but by their lead based on notes? )
9) Limit the number of heads the abovementioned overseas firms can use. > Fewer testers, less experienced, with little training, a much (ahem) 'slower' approach to testing.
Results: Client appcompat % hovering at <40% (GASP - INTERNAL INFO... better moderate this one out!!!!)
Here's an anomaly for PM's to 'splain away. If automation is such a great tool, why is it not finding more bugs than a small handful of testers in a lab on the other side of the planet?
Mgmt Response:
(CRICKETS chirping)"
this is particularly hillarious for me since my company is run exactly the same. well probably even worse, since rather than leave experienced heads to run qa for some products, they let me at the time , rather inexperienced in qa 24 year old do it. i also wrote a lot of really useless automation, to automate button clicking of the coworkers i used to do click. seeing as they were all laid off. in fact i went to a meeting last week as basically "the only one worth talking to left" in order to clarify why our product was buggy.
i think we managed to lay off or lose to another job, half of my qa team right before shipdate. even better is that i learned to write automation code, only by randomly bothering people at work, and through google and msdn. and that all the automation was written completely in win32 and not a real scripting language. because well management was "SOLD" on the idea.
and we shipped instead of say delaying i dunno for a year to rewrite the whole thing because well it sucked. in order to get holiday sales, etc. and our product sucks balls. so i see both sides of this. hahaha.
now apparently as our stock price has plummeted, management feels the need to cut costs even more. and what will happen is a beloved consumer product will be destroyed since A. it already sucks, and B. it will be QA and developed more and more by random indian guys in india who it seems could not tie their shoes unless it came with an instruction book.
some of the commenters are right though. some heads will roll. we fired some people, demoted others etc. didnt really help much since the really high up people are still there.
no way ballmer gets fired.
so i was reading that. i also work at another large software company and well all our stuff gets pushed back, everything takes 500 hoops to jump through to get done, oh and we have like 5000 program and product managers who have no clue about software and are retarded. granted there are some good ones, and those would probably be the other 2500.
here is one comment:
"
In the last 18 months this org:
1) Cut the number of testers (several times) from approx 50 to now much less than a dozen. Of course, many top performers also left MS entirely because of middle mgmt in this org.
2) Hired more PMs
3) Cut the scope of testing (anyone done any real code coverage testing lately?)
4) Cut the number of promotions in the test orgs - nothing like a little 'de-incentivization' to increase 'bad attrition'
5) Dictate that everything can and should be automated. (Ignore that eyeballs catch more in less time...) way to go Darren. Of course, you were probably lied to by your underlings, so it's not entirely your fault. Uhh, yes it is - you made the call.
6) Hire only a small handful of devs to write automation code. Oh, and don't forget to swamp them with added process and have embittered leads review their code...
7) Hire more PMs
8) Outsource all testing to non-accountable and barely trained CSG firms overseas (Ever try to translate/clarify a bug written not by a tester, but by their lead based on notes? )
9) Limit the number of heads the abovementioned overseas firms can use. > Fewer testers, less experienced, with little training, a much (ahem) 'slower' approach to testing.
Results: Client appcompat % hovering at <40% (GASP - INTERNAL INFO... better moderate this one out!!!!)
Here's an anomaly for PM's to 'splain away. If automation is such a great tool, why is it not finding more bugs than a small handful of testers in a lab on the other side of the planet?
Mgmt Response:
(CRICKETS chirping)"
this is particularly hillarious for me since my company is run exactly the same. well probably even worse, since rather than leave experienced heads to run qa for some products, they let me at the time , rather inexperienced in qa 24 year old do it. i also wrote a lot of really useless automation, to automate button clicking of the coworkers i used to do click. seeing as they were all laid off. in fact i went to a meeting last week as basically "the only one worth talking to left" in order to clarify why our product was buggy.
i think we managed to lay off or lose to another job, half of my qa team right before shipdate. even better is that i learned to write automation code, only by randomly bothering people at work, and through google and msdn. and that all the automation was written completely in win32 and not a real scripting language. because well management was "SOLD" on the idea.
and we shipped instead of say delaying i dunno for a year to rewrite the whole thing because well it sucked. in order to get holiday sales, etc. and our product sucks balls. so i see both sides of this. hahaha.
now apparently as our stock price has plummeted, management feels the need to cut costs even more. and what will happen is a beloved consumer product will be destroyed since A. it already sucks, and B. it will be QA and developed more and more by random indian guys in india who it seems could not tie their shoes unless it came with an instruction book.
some of the commenters are right though. some heads will roll. we fired some people, demoted others etc. didnt really help much since the really high up people are still there.
no way ballmer gets fired.
Facebook
Twitter