Many QA managers and practitioners haven't read anything formal or academic about QA.  They couldn't tell you what cyclomatic complexity is, or what LOC stands for, or which defect metrics are reliable indicators of software quality. All they know is what they learned by practice, which is often pretty spotty.  Some folks come into management without even having worked in QA!

QA is a technical field and it's not somehting you learn just by poking around and stumbling into bugs pretending to be a dumb user.  True QA professionals read in the discipline and truly (or at least try) understand what it's about, how it's done, how it's been done, and what the terms and concepts of the discpline are and how they've been defined by others in the past.

Do yourself a favor if you're in QA and want to stay in it for the long run, and read some of the hardcore literature of your field and stop thinking someone else will or should do it.  Anything by Boris Beizer is great.  Robert Binder's recent and humongous Testing Object-Oriented Systems is indispensable for any serious QA engineer working in OO software.  Glenford Myers' The Art of Software Testing is like the Old Testament of QA engineering.  Developers ought to read some of this stuff too.  Most developers these days seem to know jack about testing and software metrics.