Preface
In 1987, I took a job at Apple Computer as a Software Quality Assurance engineer. I was part of a 250-person QA organization. We worked on a different floor, and reported to a different VP, from development. Our jobs were mechanical and somewhat boring. Developers didn’t have a lot of respect for us. We didn’t have that much more respect for ourselves. I remember a fair number of QA engineers getting caught playing games on their computers all day and being fired as a result. I got out of QA and into development as fast as I could.
Not long after I switched departments, Apple dissolved the QA organization and embedded individual QA engineers into their respective development teams. The testers sat next to the developers, went out to lunch with them, and worked cheek-by-jowl with them. Mutual respect, job satisfaction, and quality all skyrocketed.
Since then I’ve held a variety of jobs across the Development-QA-Operations spectrum. I’ve been a consultant, a CTO, and an enterprise architect. I’ve worked for Software-as-a-Service startups, and managed hosting providers and Fortune 500 companies. I’ve led Agile, ITIL, and DevOps initiatives. Throughout all this time, my experience at Apple has always stuck with me. It taught me that, as much as anything, quality comes from dissolving boundaries, fostering cross-functional collaboration, and treating testing as an integral part of a process rather than something external to it.
Anything we write is at least partly a reflection ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access