An in-depth exploration of the effects of different steels, heat treatments, and edge geometries on knife performance. This book provides ratings for toughness, edge retention, and corrosion resistance for all of the popular knife steels. Micrographs of over 50 steels. Specific recommended heat treatments for each steel. And answers to questions like: 1) Does a thinner or thicker edge last longer? 2) What heat treatment leads to the best performance? 3) Are there performance benefits to forging blades? 4) Should I use stainless or carbon steel? All of these questions and more are answered by a metallurgist who grew up around the knife industry.

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.

An introduction to computer engineering for babies. Learn basic logic gates with hands on examples of buttons and an output LED.

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

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering. How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world’s leading practitioners construct and maintain software. This book covers Google’s unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization. You’ll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code: How time affects the sustainability of software and how to make your code resilient over time How scale affects the viability of software practices within an engineering organization What trade-offs a typical engineer needs to make when evaluating design and development decisions

Written by the author of the best-selling HyperText & HyperMedia, this book is an excellent guide to the methods of usability engineering. The book provides the tools needed to avoid usability surprises and improve product quality. Step-by-step information on which method to use at various stages during the development lifecycle are included, along with detailed information on how to run a usability test and the unique issues relating to international usability.* Emphasizes cost-effective methods that developers can implement immediately* Instructs readers about which methods to use when, throughout the development lifecycle, which ultimately helps in cost-benefit analysis. * Shows readers how to avoid the four most frequently listed reasons for delay in software projects.* Includes detailed information on how to run a usability test.* Covers unique issues of international usability.* Features an extensive bibliography allowing readers to find additional information.* Written by an internationally renowned expert in the field and the author of the best-selling HyperText & HyperMedia.

Presents an engineering guide containing a variety of mathematical and technical formulas and equations.