- Table View
- List View
What Could Possibly Go Wrong. . .
by Jeremy ClarksonWhat Could Possibly Go Wrong... is the sixth book in Jeremy Clarkson's bestselling The World According to Clarkson series.No one writes about cars like Jeremy Clarkson. While most correspondents are too buys diving straight into BHP, MPG and MPH, Jeremy appreciates that there are more important things to life. Don't worry, we'll get to the cars. Eventually. But first we should consider: · The case for invading France · The overwhelming appeal of a nice sit-down · The inconvenience of gin and tonic · Why clothes are no better than ice cream · Spot-welding with the Duchess of Kent · And why Denmark is the best place in the world Armed only with conviction, curiosity, enthusiasm and a stout pair of trousers, Jeremy hurtles around the world - along motorway, autoroute, freeway and autobahn - in search of answers to life's puzzles and ponderings without forethought or fear for his own safety. What, you have to ask, could possibly go wrong...Praise for Clarkson:'Brilliant... laugh-out-loud' Daily Telegraph'Outrageously funny... will have you in stitches' Time Out'Very funny . . . I cracked up laughing on the tube' Evening StandardJeremy Clarkson began his career on the Rotherham Advertiser. Since then he has written for the Sun, theSunday Times, the Rochdale Observer, the Wolverhampton Express & Star, all of the Associated Kent Newspapers and Lincolnshire Life. Today he is the tallest person working in British television.
What Curriculum for the Information Age
by Mary Alice WhiteFirst Published in 1987. Routledge is an imprint of Taylor & Francis, an informa company.
What Do Science, Technology, and Innovation Mean from Africa? (The\mit Press Ser.)
by Clapperton MavhungaExplorations of science, technology, and innovation in Africa not as the product of “technology transfer” from elsewhere but as the working of African knowledge.In the STI literature, Africa has often been regarded as a recipient of science, technology, and innovation rather than a maker of them. In this book, scholars from a range of disciplines show that STI in Africa is not merely the product of “technology transfer” from elsewhere but the working of African knowledge. Their contributions focus on African ways of looking, meaning-making, and creating. The chapter authors see Africans as intellectual agents whose perspectives constitute authoritative knowledge and whose strategic deployment of both endogenous and inbound things represents an African-centered notion of STI. “Things do not (always) mean the same from everywhere,” observes Clapperton Chakanetsa Mavhunga, the volume's editor. Western, colonialist definitions of STI are not universalizable.The contributors discuss topics that include the trivialization of indigenous knowledge under colonialism; the creative labor of chimurenga, the transformation of everyday surroundings into military infrastructure; the role of enslaved Africans in America as innovators and synthesizers; the African ethos of “fixing”; the constitutive appropriation that makes mobile technologies African; and an African innovation strategy that builds on domestic capacities. The contributions describe an Africa that is creative, technological, and scientific, showing that African STI is the latest iteration of a long process of accumulative, multicultural knowledge production.ContributorsGeri Augusto, Shadreck Chirikure, Chux Daniels, Ron Eglash, Ellen Foster, Garrick E. Louis, D. A. Masolo, Clapperton Chakanetsa Mavhunga, Neda Nazemi, Toluwalogo Odumosu, Katrien Pype, Scott Remer
What Do We Know About the Roswell Incident? (What Do We Know About?)
by Ben Hubbard Who HQThe What Do We Know About? series explores the mysterious, the unknown, and the unexplained. Will we ever learn the truth about what actually landed at Roswell? From the #1 New York Times Best-Selling Who Was? series comes Where Is?, a series that tells the stories of world-famous landmarks and natural wonders and features a fold-out map!In 1947, an unusual object crashed in the New Mexico desert and was recovered by the Roswell Army Airfield officers. People everywhere began to speculate what the object could be. Could it possibly be a flying saucer? Would that be proof of aliens and life beyond Earth? Even decades later, some people still believe that the Roswell Incident is the most famous UFO sighting ever. Still, those who worked at the airfield insist it was just a weather balloon that had fallen from the sky. Was the Roswell Incident evidence of alien life, a government cover-up, or just a myth? Here are the facts about what we do know about Roswell.
"What Do You Care What Other People Think?": Further Adventures of a Curious Character
by Ralph Leighton Richard P. FeynmanThe New York Times best-selling sequel to "Surely You're Joking, Mr. Feynman!" One of the greatest physicists of the twentieth century, Richard Feynman possessed an unquenchable thirst for adventure and an unparalleled ability to tell the stories of his life. "What Do You Care What Other People Think?" is Feynman's last literary legacy, prepared with his friend and fellow drummer, Ralph Leighton. Among its many tales--some funny, others intensely moving--we meet Feynman's first wife, Arlene, who taught him of love's irreducible mystery as she lay dying in a hospital bed while he worked nearby on the atomic bomb at Los Alamos. We are also given a fascinating narrative of the investigation of the space shuttle Challenger's explosion in 1986, and we relive the moment when Feynman revealed the disaster's cause by an elegant experiment: dropping a ring of rubber into a glass of cold water and pulling it out, misshapen.
What Every Engineer Should Know About Business Communication (What Every Engineer Should Know)
by John X. WangEngineers must possess a range of business communication skills that enable them to effectively communicate the purpose and relevance of their idea, process, or technical design. This unique business communication text is packed with practical advice that will improve your ability to- Market ideas Write proposals Generate enthusiasm for research De
What Every Engineer Should Know About Career Management (What Every Engineer Should Know)
by Mike FiccoThanks to their education, experience, and general philosophical orientation, many engineers fail to notice critical issues in the workplace that can directly impact their career advancement and day-to-day job satisfaction. This text focuses on career management, and the accompanying importance of human and social interactions in the office. Althou
What Every Engineer Should Know about Computer Modeling and Simulation
by Don M. IngelsThis book presents a brief description of what constitutes computer modeling and simulation with techniques given to get a feel for how some of the simulation software packages involving hundreds of thousands of lines of code were developed.
What Every Engineer Should Know about Concurrent Engineering
by Thomas A. SalomoneThis work offers a step-by-step approach to the overall concurrent engineering (CE) development process, presenting both fundamental principles and advanced concepts, while focusing on rapid product development and cost-effective designs. The book also provides an introduction to Cost Driven Design, with specific examples on how to minimize expenses by understanding the basis of product costs. The process of concurrent engineering is explained from initial planning to production start-up.
What Every Engineer Should Know about Data Communications
by Carl Stephen CliftonThis book discusses the fundamentals of data communications, the most important element in an engineer's daily function. It examines the technologies and methodologies now available in the marketplace to effect the exchange of information.
What Every Engineer Should Know About Developing Real-Time Embedded Products (What Every Engineer Should Know)
by Kim R. FowlerYou can find them in your wristwatch or MP3 player; they perform specific functions in washing machines, traffic lights, and even pacemakers. Embedded systems are pervasive, ubiquitous, and widespread throughout our daily lives. Developing these real-time embedded products requires an understanding of the interactions between different disciplines,
What Every Engineer Should Know About Digital Accessibility (ISSN)
by Sarah Horton David SloanAccessibility is a core quality of digital products to be deliberately addressed throughout the development lifecycle. What Every Engineer Should Know About Digital Accessibility will prepare readers to integrate digital accessibility into their engineering practices. Readers will learn how to accurately frame accessibility as an engineering challenge so they are able to address the correct problems in the correct way.Illustrated with diverse perspectives from accessibility practitioners and advocates, this book describes how people with disabilities use technology, the nature of accessibility barriers in the digital world, and the role of engineers in breaking down those barriers. Accessibility competence for current, emerging, and future technologies is addressed through a combination of guiding principles, core attributes and requirements, and accessibility‑informed engineering practices.FEATURES Discusses how technology can support inclusion for people with disabilities and how rigorous engineering processes help create quality user experiences without introducing accessibility barriers Explains foundational principles and guidelines that build core competency in digital accessibility as they are applied across diverse and emerging technology platforms Highlights practical insights into how engineering teams can effectively address accessibility throughout the technology development lifecycle Uses international standards to define and measure accessibility quality Written to be accessible to non‑experts in the subject area, What Every Engineer Should Know About Digital Accessibility is aimed at students, professionals, and researchers in the field of software engineering.
What Every Engineer Should Know about Ethics (What Every Engineer Should Know)
by Kenneth K. HumphreysThis compact reference succinctly explains the engineering profession's codes of ethics using case studies drawn from decisions of the National Society of Professional Engineers' Board of Ethical Review, examining ethical challenges in engineering, construction, and project management. It includes study questions to supplement general engineering survey courses and a list of references to aid practicing engineers in exploring topics in depth. The author discusses recent headline-making disasters such as the Challenger explosion and the Chernobyl nuclear catastrophe; considers the merits and drawbacks of professional codes of ethics; and outlines legal standards for liability.
What Every Engineer Should Know About Excel (What Every Engineer Should Know #50)
by J. P. Holman Blake K. Holman<p>Understanding the powerful computational and graphics capabilities of Microsoft Excel is an enormous benefit to engineers and technical professionals in almost any field and at all levels of experience. What Every Engineer Should Know About Excel is a practical guide to unlocking the features and functions of this program, using examples and screenshots to walk readers through the steps to build a strong understanding of the material. <p>This second edition is updated to reflect the latest version of Excel (2016) and expands its scope to include data management, connectivity to external data sources, and integration with "the cloud" for optimal use of the Excel product. It also introduces the ribbon bar navigation prevalent in Microsoft products beginning with the 2007 version of MS Office. Covering a variety of topics in self-contained chapters, this handy guide will also prove useful for professionals in IT, finance, and real estate.</p>
What Every Engineer Should Know about Inventing
by William H. MiddendorfThis book provides the reader with the information they need to develop into a person who seeks creative opportunities and responds with elegant inventions. It is intended for young inventor and to all those who have the talent and the desire to invent.
What Every Engineer Should Know about MATLAB and Simulink (ISSN)
by Adrian B. BiranUsing examples from mathematics, mechanical and electrical engineering, and control and signal processing, this book provides an introduction to MATLAB and Simulink and examines the advantages and limitations of both. The author demonstrates how to visualize the results of calculations in various kinds of graphical representations, how to write useful script files and functions for solving specific problems, how to avoid disastrous, computational errors, and how to insert calculations and graphs into technical reports produced by either MS Word or LaTeX. Companion software with functions and script files are available online.
What Every Engineer Should Know about Microcomputer Software
by Keith A. WehmeyerThis book covers the entire scope of computer programming and Structured Program Design, from problem identification to maintaining existing programs. It is intended for two audiences: beginning programmers and experienced programmers seeking ways to improve the quality of their software.
What Every Engineer Should Know about Microcomputers: Hardware/Software Design: a Step-by-step Example, Second Edition,
by William S. Bennett Carl F. Evert Jr. Leslie C. LanderRevised and expanded guide demonstrates microcomputer usage by working through one simple design challenge and explaining its solution. This edition features the contributions of an Ada expert, demonstrates (in 14 new chapters) the development of a microcomputer system structured by this language.
What Every Engineer Should Know About Modeling and Simulation (What Every Engineer Should Know)
by Raymond J. Madachy Daniel HoustonThis practical book presents fundamental concepts and issues in computer modeling and simulation (M&S) in a simple and practical way for engineers, scientists, and managers who wish to apply simulation successfully to their real-world problems. It offers a concise approach to the coverage of generic (tool-independent) M&S concepts and enables engineering practitioners to easily learn, evaluate, and apply various available simulation concepts. Worked out examples are included to illustrate the concepts and an example modeling application is continued throughout the chapters to demonstrate the techniques. The book discusses modeling purposes, scoping a model, levels of modeling abstraction, the benefits and cost of including randomness, types of simulation, and statistical techniques. It also includes a chapter on modeling and simulation projects and how to conduct them for customer and engineer benefit and covers the stages of a modeling and simulation study, including process and system investigation, data collection, modeling scoping and production, model verification and validation, experimentation, and analysis of results.
What Every Engineer Should Know about Patents
by William G. Konold"This useful, authoritative volume focuses on all aspects of intellectual property law with particular emphasis on patent laws enabling the reader to avoid such pitfalls as a loss of rights, and establish valid rights in inventions, trademarks, and writings. "
What Every Engineer Should Know about Practical Cad/cam Applications
by John StarkThis book presents basic information on CAD/CAM and describes how to select, implement, and run a CAD/CAM system in the mechanical engineering environment. It also describes the overall state of CAD/CAM today in different industrial sectors and for different manufacturing technologies.
What Every Engineer Should Know About Project Management
by Arnold M. Ruskin W. Eugene EstesCovering the roles and responsibilities of the project manager, this second edition describes requirement specifications, work breakdown structures, project control and risk management, and offers new information on motivation, matrix arrangements, and project records. Discussing the anatomy of a project planning and control and techniques, the aut
What Every Engineer Should Know about Reliability and Risk Analysis (What Every Engineer Should Know #30)
by Mohammad Modarres"Examining reliability, availability, and risk analysis and reviewing in probability and statistics essential to understanding reliability methods, this outstanding volume describes day-to-day techniques used by practicing engineers -- discussing important reliability aspects of both components and complex systems. "
What Every Engineer Should Know About Risk Engineering and Management (ISSN)
by John X. WangCompletely updated, this new edition uniquely explains how to assess and handle technical risk, schedule risk, and cost risk efficiently and effectively for complex systems that include Artificial Intelligence, Machine Learning, and Deep Learning. It enables engineering professionals to anticipate failures and highlight opportunities to turn failure into success through the systematic application of Risk Engineering. What Every Engineer Should Know About Risk Engineering and Management, Second Edition discusses Risk Engineering and how to deal with System Complexity and Engineering Dynamics, as it highlights how AI can present new and unique ways that failures can take place. The new edition extends the term "Risk Engineering" introduced by the first edition, to Complex Systems in the new edition. The book also relates Decision Tree which was explored in the first edition to Fault Diagnosis in the new edition and introduces new chapters on System Complexity, AI, and Causal Risk Assessment along with other chapter updates to make the book current. Features Discusses Risk Engineering and how to deal with System Complexity and Engineering Dynamics Highlights how AI can present new and unique ways of failure that need to be addressed Extends the term "Risk Engineering" introduced by the first edition to Complex Systems in this new edition Relates Decision Tree which was explored in the first edition to Fault Diagnosis in the new edition Includes new chapters on System Complexity, AI, and Causal Risk Assessment along with other chapters being updated to make the book more current The audience is the beginner with no background in Risk Engineering and can be used by new practitioners, undergraduates, and first-year graduate students.
What Every Engineer Should Know About Risk Engineering and Management (ISSN #Vol. 36)
by John X. Wang Marvin L. Roush"Explains how to assess and handle technical risk, schedule risk, and cost risk efficiently and effectively--enabling engineering professionals to anticipate failures regardless of system complexity--highlighting opportunities to turn failure into success."