An account of conflicts within engineering in the 1960s that helped shape our dominant contemporary understanding of technological change as the driver of history. In the late 1960s an eclectic group of engineers joined the antiwar and civil rights activists of the time in agitating for change. The engineers were fighting to remake their profession, challenging their fellow engineers to embrace a more humane vision of technology. In Engineers for Change, Matthew Wisnioski offers an account of this conflict within engineering, linking it to deep-seated assumptions about technology and American life. The postwar period in America saw a near-utopian belief in technology's beneficence. Beginning in the mid-1960s, however, society—influenced by the antitechnology writings of such thinkers as Jacques Ellul and Lewis Mumford—began to view technology in a more negative light. Engineers themselves were seen as conformist organization men propping up the military-industrial complex. A dissident minority of engineers offered critiques of their profession that appropriated concepts from technology's critics. These dissidents were criticized in turn by conservatives who regarded them as countercultural Luddites. And yet, as Wisnioski shows, the radical minority spurred the professional elite to promote a new understanding of technology as a rapidly accelerating force that our institutions are ill-equipped to handle. The negative consequences of technology spring from its very nature—and not from engineering's failures. “Sociotechnologists” were recruited to help society adjust to its technology. Wisnioski argues that in responding to the challenges posed by critics within their profession, engineers in the 1960s helped shape our dominant contemporary understanding of technological change as the driver of history.

An account of conflicts within engineering in the 1960s that helped shape our dominant contemporary understanding of technological change as the driver of history. In the late 1960s an eclectic group of engineers joined the antiwar and civil rights activists of the time in agitating for change. The engineers were fighting to remake their profession, challenging their fellow engineers to embrace a more humane vision of technology. In Engineers for Change, Matthew Wisnioski offers an account of this conflict within engineering, linking it to deep-seated assumptions about technology and American life. The postwar period in America saw a near-utopian belief in technology's beneficence. Beginning in the mid-1960s, however, society—influenced by the antitechnology writings of such thinkers as Jacques Ellul and Lewis Mumford—began to view technology in a more negative light. Engineers themselves were seen as conformist organization men propping up the military-industrial complex. A dissident minority of engineers offered critiques of their profession that appropriated concepts from technology's critics. These dissidents were criticized in turn by conservatives who regarded them as countercultural Luddites. And yet, as Wisnioski shows, the radical minority spurred the professional elite to promote a new understanding of technology as a rapidly accelerating force that our institutions are ill-equipped to handle. The negative consequences of technology spring from its very nature—and not from engineering's failures. “Sociotechnologists” were recruited to help society adjust to its technology. Wisnioski argues that in responding to the challenges posed by critics within their profession, engineers in the 1960s helped shape our dominant contemporary understanding of technological change as the driver of history.

A leading scientist argues that we must consider deploying climate engineering technology to slow the pace of global warming. Climate engineering—which could slow the pace of global warming by injecting reflective particles into the upper atmosphere—has emerged in recent years as an extremely controversial technology. And for good reason: it carries unknown risks and it may undermine commitments to conserving energy. Some critics also view it as an immoral human breach of the natural world. The latter objection, David Keith argues in A Scientist's Case for Climate Engineering, is groundless; we have been using technology to alter our environment for years. But he agrees that there are large issues at stake. A leading scientist long concerned about climate change, Keith offers no naïve proposal for an easy fix to what is perhaps the most challenging question of our time; climate engineering is no silver bullet. But he argues that after decades during which very little progress has been made in reducing carbon emissions we must put this technology on the table and consider it responsibly. That doesn't mean we will deploy it, and it doesn't mean that we can abandon efforts to reduce greenhouse gas emissions. But we must understand fully what research needs to be done and how the technology might be designed and used. This book provides a clear and accessible overview of what the costs and risks might be, and how climate engineering might fit into a larger program for managing climate change.

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

Guidelines for the Management of Change for Process Safety provides guidance on the implementation of effective and efficient Management of Change (MOC) procedures, which can be applied to improve process safety. In addition to introducing MOC systems, the book describes how to design an initial system from scratch, including the scope of the system and the applications over a plant life cycle and the boundaries and overlaps with other process safety management systems. Note: CD-ROM/DVD and other supplementary materials are not included as part of eBook file.

Climate Adaptation Engineering defines the measures taken to reduce vulnerability and increase the resiliency of built infrastructure. This includes enhancement of design standards, structural strengthening, utilisation of new materials, and changes to inspection and maintenance regimes, etc. The book examines the known effects and relationships of climate change variables on infrastructure and risk-management policies. Rich with case studies, this resource will enable engineers to develop a long-term, self-sustained assessment capacity and more effective risk-management strategies. The book's authors also take a long-term view, dealing with several aspects of climate change. The text has been written in a style accessible to technical and non-technical readers with a focus on practical decision outcomes. - Provides climate scenarios and their likelihoods, hazard modelling (wind, flood, heatwaves, etc.), infrastructure vulnerability, resilience or exposure (likelihood and extent of damage) - Introduces the key concepts needed to assess the risks, costs and benefits of future proofing infrastructures in a changing climate - Includes case studies authored by experts from around the world

The Global Engineers: Building a Safe and Equitable World Together, is inspired by the opportunities for engineers to contribute to global prosperity. This book presents a vision for Global Engineering, and identifies that engineers should be concerned with the unequal and unjust distribution of access to basic services, such as water, sanitation, energy, food, transportation, and shelter. As engineers, we should place an emphasis on identifying the drivers, determinants, and solutions to increasing equitable access to reliable services. Global Engineering envisions a world where everyone has safe water, sanitation, energy, food, shelter, and infrastructure, and can live in health, dignity, and prosperity. This book seeks to examine the role and ultimately the impact of engineers in global development. Engineers are solutions-oriented people. We enjoy the opportunity to identify a product or need, and design appropriate technical solutions. However, the structural and historical barriers to global prosperity requires that Engineers focus more broadly on improving the tools and practice of poverty reduction and that we include health, economics, policy, and governance as relevant expertise with which we are conversant. Engineers must become activists and advocates, rejecting ahistorical technocratic approaches that suggest poverty can be solved without justice or equity. Engineers must leverage our professional skills and capacity to generate evidence and positive impact toward rectifying inequalities and improving lives. Half of this book is dedicated to profiles of engineers and other technical professionals who have dedicated their careers to searching for solutions to global development challenges. These stories introduce the reader to the diverse opportunities and challenges in Global Engineering.

A Revolution Is Coming. It Isn't What You Think.This book tells the improbable stories of Franklin W. Olin College of Engineering, a small startup in Needham, Massachusetts, with aspirations to be a beacon to engineering education everywhere, and the iFoundry incubator at the University of Illinois, an unfunded pilot program with aspirations to change engineering at a large public university that wasn't particularly interested in changing. That either one survived is story enough, but what they found out together changes the course of education transformation forever: - How joy, trust, openness, and connec- tion are the keys to unleashing young, courageous engineers.- How engineers educated in narrow technical terms with a fixed mindset need an education that actively engages six minds-analytical, design, people, linguistic, body, and mindful- using a growth mindset.- How emotion and culture are the crucial elements of change, not content, curriculum, and pedagogy.- How four technologies of trust are well established and widely available to promote more rapid academic change.- How all stakeholders can join together in a movement of open innovation to accelerate collaborative disruption of the status quo.Read this book and get a glimpse inside the coming revolution in engineering. Feel the engaging stories in this book and understand the depth of change that is coming. Use this book to help select, shape, demand, and create educational experiences aligned with the creative imperative of the twenty-first century.

A multidisciplinary introduction to sustainable engineering exploring challenges and solutions through practical examples and exercises.

At most technology companies, you'll reach Senior Software Engineer, the career level for software engineers, in five to eight years. At that career level, you'll no longer be required to work towards the next pro? motion, and being promoted beyond it is exceptional rather than ex? pected. At that point your career path will branch, and you have to decide between remaining at your current level, continuing down the path of technical excellence to become a Staff Engineer, or switching into engineering management. Of course, the specific titles vary by company, and you can replace "Senior Engineer" and "Staff Engineer" with whatever titles your company prefers.Over the past few years we've seen a flurry of books unlocking the en? gineering management career path, like Camille Fournier's The Man? ager's Path, Julie Zhuo's The Making of a Manager, Lara Hogan's Re? silient Management and my own, An Elegant Puzzle. The manage? ment career isn't an easy one, but increasingly there are maps avail? able for navigating it.On the other hand, the transition into Staff Engineer, and its further evolutions like Principal and Distinguished Engineer, remains chal? lenging and undocumented. What are the skills you need to develop to reach Staff Engineer? Are technical abilities alone sufficient to reach and succeed in that role? How do most folks reach this role? What is your manager's role in helping you along the way? Will you enjoy being a Staff Engineer or you will toil for years to achieve a role that doesn't suit you?"Staff Engineer: Leadership beyond the management track" is a pragmatic look at attaining and operate in these Staff-plus roles.