We'd have to ask David to clarify, but from what he's posted, his
responsibilities seem to extend beyond just finding the issues, yes...David?
On 4/3/2011 10:01 AM, Donald J. Organ IV wrote:
So what your saying is after your QS person finds issues, they go into
the code/design and fix it themselves??
------------------------------------------------------------------------
*From: *"Kristina Anderson" <k...@kacomputerconsulting.com>
*To: *"NYPHP Talk" <talk@lists.nyphp.org>
*Sent: *Sunday, April 3, 2011 7:10:42 AM
*Subject: *Re: [nyphp-talk] How much is a site redesign worth?
The decision on what to build comes down from on high where some
confab of management pinheads make decisions based on "wow this will
make us rich if we hire some cheap labor to build it for us" and "my
Uncle Frank told me PHP was the way to go while we were golfing last
week".
The tech lead then assembles a team of inexperienced, cheap
programmers (because management has decided the budget, too) who crank
out a horrifying batch of really awful code that kind of looks like it
might do what management requested be built, with the tech lead taking
all the credit for anything good that might happen along the way, and
blaming the programmers he personally likes the least for whatever bad
things inevitably occur.
This poo poo stew then gets dumped into the lap of our hapless "QA
Analyst" who is expected to work a miracle on par with parting the Red
Sea by turning it into Tasty Texas Chili for distribution to the masses.
Kristina
\\On 4/3/2011 2:01 AM, Frank Cefalu wrote:
Not saying your tasks are easier or less stressful.
But, I guess you can look at senior devs/leads as the architect of
the house, and your the house inspector.
Get what I mean? Not saying one out weighs the other, just one is
more involved in architecture, and the other is involved in making
sure it meets city requirements aka business reqs.
----
*Frank Cefalu*
On Sat, Apr 2, 2011 at 9:21 PM, David Krings <ram...@gmx.net
<mailto:ram...@gmx.net>> wrote:
On 4/2/2011 8:22 PM, Frank Cefalu wrote:
You are wrong. The work of a qa analyst is alot simpler.
You don't need to do
any architecture based on traffic retention, judge
framework usage etc.
Not in my QA world....
David
_______________________________________________
New York PHP Users Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/Show-Participation
_______________________________________________
New York PHP Users Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/Show-Participation
_______________________________________________
New York PHP Users Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/Show-Participation
_______________________________________________
New York PHP Users Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/Show-Participation
--
Kristina Anderson
PHP/MySQL/LAMP/AJAX Systems Analyst / Programmer / Consultant
646 247 4987
_______________________________________________
New York PHP Users Group Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
http://www.nyphp.org/Show-Participation
