For this special hardcover edition, two new appendixes on locales and standard library exception safety (also available at www.research.att.com/ bs/) have been added. The result is complete, authoritative coverage of the C++ language, its standard library, and key design techniques. Based on the ANSI/ISO C++ standard, The C++ Programming Language provides current and comprehensive coverage of all C++ language features and standard library components. For example:abstract classes as interfaces class hierarchies for object-oriented programming templates as the basis for type-safe generic software exceptions for regular error handling namespaces for modularity in large-scale software run-time type identification for loosely coupled systems the C subset of C++ for C compatibility and system-level work standard containers and algorithms standard strings, I/O streams, and numerics C compatibility, internationalization, and exception safety Bjarne Stroustrup makes C++ even more accessible to those new to the language, while adding advanced information and techniques that even expert C++ programmers will find invaluable.

    You will be able to look over the shoulder of major coding and design experts to see problems through their eyes.This is not simply another design patterns book, or another software engineering treatise on the right and wrong way to do things. The authors think aloud as they work through their project's architecture, the tradeoffs made in its construction, and when it was important to break rules. Beautiful Code is an opportunity for master coders to tell their story. All author royalties will be donated to Amnesty International.

    In its sweeping survey of the history of Internet search technologies, its gossip about and analysis of Google, and its speculation on the larger cultural implications of a Web-connected world, it will likely receive attention from a variety of businesspeople, technology futurists, journalists, and interested observers of mid-2000s zeitgeist. This ambitious book comes with a strong pedigree. Author John Battelle was a founder of The Industry Standard and then one of the original editors of Wired, two magazines which helped shape our early perceptions of the wild world of the Internet. Battelle clearly drew from his experience and contacts in writing The Search. In addition to the sure-handed historical perspective and easy familiarity with such dot-com stalwarts as AltaVista, Lycos, and Excite, he speckles his narrative with conversational asides from a cast of fascinating characters, such Google's founders, Larry Page and Sergey Brin; Yahoo's, Jerry Yang and David Filo; key executives at Microsoft and different VC firms on the famed Sandhill road; and numerous other insiders, particularly at the company which currently sits atop the search world, Google. The Search is not exactly the corporate history of Google. At the book's outset, Battelle specifically indicates his desire to understand what he calls the cultural anthropology of search, and to analyze search engines' current role as the "database of our intentions"--the repository of humanity's curiosity, exploration, and expressed desires. Interesting though that beginning is, though, Battelle's story really picks up speed when he starts dishing inside scoop on the darling business story of the decade, Google. To Battelle's credit, though, he doesn't stop just with historical retrospective: the final part of his book focuses on the potential future directions of Google and its products' development. In what Battelle himself acknowledges might just be a "digital fantasy train", he describes the possibility that Google will become the centralizing platform for our entire lives and quotes one early employee on the weightiness of Google's potential impact: "Sometimes I feel like I am on a bridge, twenty thousand feet up in the air. If I look down I'm afraid I'll fall. I don't feel like I can think about all the implications." Some will shrug at such words; after all, similar hype has accompanied other technologies and other companies before. Many others, though, will search Battelle's story for meaning--and fast. --Peter Han

    How's that possible? Google revealed the secret through a project called Kubernetes, an open source cluster orchestrator (based on its internal Borg system) that radically simplifies the task of building, deploying, and maintaining scalable distributed systems in the cloud. This practical guide shows you how Kubernetes and container technology can help you achieve new levels of velocity, agility, reliability, and efficiency.Authors Kelsey Hightower, Brendan Burns, and Joe Beda--who've worked on Kubernetes at Google--explain how this system fits into the lifecycle of a distributed application. You will learn how to use tools and APIs to automate scalable distributed systems, whether it is for online services, machine-learning applications, or a cluster of Raspberry Pi computers.Explore the distributed system challenges that Kubernetes addressesDive into containerized application development, using containers such as DockerCreate and run containers on Kubernetes, using Docker's Image format and container runtimeExplore specialized objects essential for running applications in productionReliably roll out new software versions without downtime or errorsGet examples of how to develop and deploy real-world applications in Kubernetes

    If you're one of them, The Scrum Field Guide will give you skills and confidence to adopt Scrum more rapidly, more successfully, and with far less pain and fear. Long-time Scrum practitioner Mitch Lacey identifies major challenges associated with early-stage Scrum adoption, as well as deeper issues that emerge after companies have adopted Scrum, and describes how other organizations have overcome them. You'll learn how to gain "quick wins" that build support, and then use the flexibility of Scrum to maximize value creation across the entire process. In 30 brief, engaging chapters, Lacey guides you through everything from defining roles to setting priorities to determining team velocity, choosing a sprint length, and conducting customer reviews. Along the way, he explains why Scrum can seem counterintuitive, offers a solid grounding in the core agile concepts that make it work, and shows where it can (and shouldn't) be modified. Coverage includes Getting teams on board, and bringing new team members aboard after you've started Creating a "definition of done" for the team and organization Implementing the strong technical practices that are indispensable for agile success Balancing predictability and adaptability in release planning Keeping defects in check Running productive daily standup meetings Keeping people engaged with pair programming Managing culture clashes on Scrum teams Performing "emergency procedures" to get sprints back on track Establishing a pace your team can truly sustain Accurately costing projects, and measuring the value they deliver Documenting Scrum projects effectively Prioritizing and estimating large backlogs Integrating outsourced and offshored components Packed with real-world examples from Lacey's own experience, this book is invaluable to everyone transitioning to agile: developers, architects, testers, managers, and project owners alike.

    Edited by the Sustainability Institute’s Diana Wright, this essential primer brings systems thinking out of the realm of computers and equations and into the tangible world, showing readers how to develop the systems-thinking skills that thought leaders across the globe consider critical for 21st-century life.Some of the biggest problems facing the world—war, hunger, poverty, and environmental degradation—are essentially system failures. They cannot be solved by fixing one piece in isolation from the others, because even seemingly minor details have enormous power to undermine the best efforts of too-narrow thinking.While readers will learn the conceptual tools and methods of systems thinking, the heart of the book is grander than methodology. Donella Meadows was known as much for nurturing positive outcomes as she was for delving into the science behind global dilemmas. She reminds readers to pay attention to what is important, not just what is quantifiable, to stay humble, and to stay a learner.In a world growing ever more complicated, crowded, and interdependent, Thinking in Systems helps readers avoid confusion and helplessness, the first step toward finding proactive and effective solutions.

    This is the story of a technical genius who, against all odds, created a series of machines that revolutionized the computing industry. Chronicling each major breakthrough, Murray takes us behind the scenes to witness late-night brainstorming sessions, miraculous eleventh-hour fixes, and flashes of insight when bold new ideas were cooked up. Drawing from rare in-depth interviews with Seymour Cray, Murray gives us an unparalleled portrait of the man and his methods, reporting not only Cray's personal reflections, but the recollections of his closest colleagues and the truth behind the rumors.

    Before Apple, IBM, or Dell, Commodore was the first computer maker to market its machines to the public, selling an estimated 22 million Commodore 64s. These halcyon days were tumultuous, however, owing to the expectations and unsparing tactics of founder Jack Tramiel. Engineers and managers with the company between 1976 and 1994 share their experiences of the groundbreaking moments, soaring business highs, and stunning employee turnover that came along with being on top of the PC world in the early days.

    But developing these systems brings its own set of headaches. With lots of examples and practical advice, this book takes a holistic view of the topics that system architects and administrators must consider when building, managing, and evolving microservice architectures.Microservice technologies are moving quickly. Author Sam Newman provides you with a firm grounding in the concepts while diving into current solutions for modeling, integrating, testing, deploying, and monitoring your own autonomous services. You'll follow a fictional company throughout the book to learn how building a microservice architecture affects a single domain.Discover how microservices allow you to align your system design with your organization's goalsLearn options for integrating a service with the rest of your systemTake an incremental approach when splitting monolithic codebasesDeploy individual microservices through continuous integrationExamine the complexities of testing and monitoring distributed servicesManage security with user-to-service and service-to-service modelsUnderstand the challenges of scaling microservice architectures

    More and more frequently, ScrumMasters and project managers are being asked to coach agile teams. But it's a challenging role. It requires new skills--as well as a subtle understanding of when to step in and when to step back. Migrating from "command and control" to agile coaching requires a whole new mind-set. In Coaching Agile Teams, Lyssa Adkins gives agile coaches the insights they need to adopt this new mind-set and to guide teams to extraordinary performance in a re-energized work environment. You'll gain a deep view into the role of the agile coach, discover what works and what doesn't, and learn how to adapt powerful skills from many allied disciplines, including the fields of professional coaching and mentoring. Coverage includes Understanding what it takes to be a great agile coach Mastering all of the agile coach's roles: teacher, mentor, problem solver, conflict navigator, and performance coach Creating an environment where self-organized, high-performance teams can emerge Coaching teams past cooperation and into full collaboration Evolving your leadership style as your team grows and changes Staying actively engaged without dominating your team and stunting its growth Recognizing failure, recovery, and success modes in your coaching Getting the most out of your own personal agile coaching journey Whether you're an agile coach, leader, trainer, mentor, facilitator, ScrumMaster, project manager, product owner, or team member, this book will help you become skilled at helping others become truly great. What could possibly be more rewarding?

    For more than twenty-five years, Malone has dominated the cable television industry, shaping the world of entertainment and communications, first with his cable company TCI and later with Liberty Media. Written with Malone's unprecedented cooperation, the engaging narrative brings this controversial capitalist and businessman to life. Cable Cowboy is at once a penetrating portrait of Malone's complex persona, and a captivating history of the cable TV industry. Told in a lively style with exclusive details, the book shows how an unassuming copper strand started as a backwoods antenna service and became the digital nervous system of the U.S., an evolution that gave U.S. consumers the fastest route to the Internet. Cable Cowboy reveals the forces that propelled this pioneer to such great heights, and captures the immovable conviction and quicksilver mind that have defined John Malone throughout his career.

    In the 1987 Nintendo Entertainment System videogame Zelda II: The Adventure of Link, a character famously declared: I AM ERROR. Puzzled players assumed that this cryptic mesage was a programming flaw, but it was actually a clumsy Japanese-English translation of "My Name is Error," a benign programmer's joke. In I AM ERROR Nathan Altice explores the complex material histories of the Nintendo Entertainment System (and its Japanese predecessor, the Family Computer), offering a detailed analysis of its programming and engineering, its expressive affordances, and its cultural significance.Nintendo games were rife with mistranslated texts, but, as Altice explains, Nintendo's translation challenges were not just linguistic but also material, with consequences beyond simple misinterpretation. Emphasizing the technical and material evolution of Nintendo's first cartridge-based platform, Altice describes the development of the Family Computer (or Famicom) and its computational architecture; the "translation" problems faced while adapting the Famicom for the U.S. videogame market as the redesigned Entertainment System; Nintendo's breakthrough console title Super Mario Bros. and its remarkable software innovations; the introduction of Nintendo's short-lived proprietary disk format and the design repercussions on The Legend of Zelda; Nintendo's efforts to extend their console's lifespan through cartridge augmentations; the Famicom's Audio Processing Unit (APU) and its importance for the chiptunes genre; and the emergence of software emulators and the new kinds of play they enabled.

    As technology companies succeed and grow, so do their engineering departments. In your career, you’ll may suddenly get the opportunity to lead teams: to become a manager. But this is often uncharted territory. How can you decide whether this career move is right for you? And if you do, what do you need to learn to succeed? Where do you start? How do you know that you’re doing it right? What does “it” even mean? And isn’t management a dirty word? This book will share the secrets you need to know to manage engineers successfully.

    

    Banks, telecommunications companies, and critical government networks (including the British Parliament and the French and German military) were infected. No one had ever seen anything like it. By January 2009 the worm lay hidden in at least eight million computers and the botnet of linked computers that it had created was big enough that an attack might crash the world. This is the gripping tale of the group of hackers, researches, millionaire Internet entrepreneurs, and computer security experts who united to defend the Internet from the Conficker worm: the story of the first digital world war.