Legendary game designer and author of the classic "A Theory of Fun for Game Design," Raph Koster is back with his first volume of selected essays. "Postmortems" collects new material and classic writings to provide a history of the development of virtual worlds, including behind-the-scenes glimpses of Ultima Online, Star Wars Galaxies, and more.

The popular Postmortem column in Game Developer magazine features firsthand accounts of how some of the most important and successful games of recent years have been made. This book offers the opportunity to harvest this expertise with one volume. The editor has organized the articles by theme and added previously unpublished analysis to reveal successful management techniques. Readers learn how superstars of the game industry like Peter Molyneux and Warren Spector have dealt with the development challenges such as managing complexity, software and game design issues, schedule challenges, and changing staff needs.

Discover the “dazzling…fascinating” (Los Angeles Times) forensic thriller that launched the New York Times bestselling Kay Scarpetta series from #1 bestselling crime writer Patricia Cornwell. Under cover of night in Richmond, Virginia, a monster strikes, leaving a gruesome trail of stranglings that has paralyzed the city. Medical examiner Kay Scarpetta suspects the worst: a deliberate campaign by a brilliant serial killer whose signature offers precious few clues. With an unerring eye, she calls on the latest advances in forensic research to unmask the madman. But this investigation will test Kay like no other, because it’s being sabotaged from within—and someone wants her dead.

As elected coroners came to be replaced by medical examiners with scientific training, the American public became fascinated with their work. From the grisly investigations showcased on highly rated television shows like C.S.I. to the bestselling mysteries that revolve around forensic science, medical examiners have never been so visible—or compelling. They, and they alone, solve the riddle of suspicious death and the existential questions that come with it. Why did someone die? Could it have been prevented? Should someone be held accountable? What are the implications of ruling a death a suicide, a homicide, or an accident? Can medical examiners unmask the perfect crime? Postmortem goes deep inside the world of medical examiners to uncover the intricate web of pathological, social, legal, and moral issues in which they operate. Stefan Timmermans spent years in a medical examiner’s office, following cases, interviewing examiners, and watching autopsies. While he relates fascinating cases here, he is also more broadly interested in the cultural authority and responsibilities that come with being a medical examiner. Although these professionals attempt to remain objective, medical examiners are nonetheless responsible for evaluating subtle human intentions. Consequently, they may end—or start—criminal investigations, issue public health alerts, and even cause financial gain or harm to survivors. How medical examiners speak to the living on behalf of the dead, is Timmermans’s subject, revealed here in the day-to-day lives of the examiners themselves.

In 2016, Google’s Site Reliability Engineering book ignited an industry discussion on what it means to run production services today—and why reliability considerations are fundamental to service design. Now, Google engineers who worked on that bestseller introduce The Site Reliability Workbook, a hands-on companion that uses concrete examples to show you how to put SRE principles and practices to work in your environment. This new workbook not only combines practical examples from Google’s experiences, but also provides case studies from Google’s Cloud Platform customers who underwent this journey. Evernote, The Home Depot, The New York Times, and other companies outline hard-won experiences of what worked for them and what didn’t. Dive into this workbook and learn how to flesh out your own SRE practice, no matter what size your company is. You’ll learn: How to run reliable services in environments you don’t completely control—like cloud Practical applications of how to create, monitor, and run your services via Service Level Objectives How to convert existing ops teams to SRE—including how to dig out of operational overload Methods for starting SRE from either greenfield or brownfield

The overwhelming majority of a software system’s lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems? In this collection of essays and articles, key members of Google’s Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You’ll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient—lessons directly applicable to your organization. This book is divided into four sections: Introduction—Learn what site reliability engineering is and why it differs from conventional IT industry practices Principles—Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE) Practices—Understand the theory and practice of an SRE’s day-to-day work: building and operating large distributed computing systems Management—Explore Google's best practices for training, communication, and meetings that your organization can use

Imagine you had to write a postmortem containing statements like these? "We were unable to resolve the outage as quickly as we would have hoped because our decision making was impacted by extreme stress." "We spent two hours repeatedly applying the fix that worked during the previous outage, only to find out that it made no difference in this one." "We did not communicate openly about an escalating outage that was caused by our botched deployment because we thought we were about to lose our jobs." While the above scenarios are entirely realistic, it's hard to find many postmortem write-ups that even hint at these "human factors." Their absence is, in part, due to the social stigma associated with publicly acknowledging their contribution to outages. And yet, people dealing with outages are clearly subject to physical exhaustion and psychological stress, not to mention impaired reasoning due to a host of cognitive biases. This report focuses on the effects and mitigation of stress and cognitive biases during outages and postmortems. This "human postmortem" is as important as the technical one, as it enables building more resilient systems and teams, and ultimately reduces the duration and severity of outages.