Engineering

Engineering explained from the ground up, with no advanced math required. This introduction to engineering shows you how bridges stay standing, why software fails, and how a vague problem becomes something that works the first time. The book moves from the basic question of what engineers actually do, through the design process, systems thinking, project money and risk, professional ethics, and where the field is going next. Every concept is tied to a real project or a real failure, so the ideas stay with you. The aluminum can that dropped from 85 grams to 13. The Brooklyn Bridge that Emily Warren Roebling ran for eleven years. The trade-offs are honest too, since you can usually make something cheaper, faster, or better, but not all three. The chapters cover: - What separates engineering from science, and how the field went from craft knowledge traded between apprentices to a licensed profession with accredited degrees and codes of conduct - The engineering method: framing a problem, gathering constraints, prototyping early, and the difference between verification and validation - Statics, dynamics, thermodynamics, materials, and dimensional analysis, including the metric and imperial mix-up that destroyed a 125 million dollar Mars orbiter in 1999 - Mechanical, civil and structural, electrical, chemical, and software engineering, and how all five meet inside one modern car - Concept generation, trade-off analysis, computer-aided design, failure modes, and design for manufacturability - Systems thinking, feedback loops, redundancy, and single points of failure, with the James Webb Space Telescope as the extreme case of a machine that had to unfold correctly a million and a half kilometers from any possible repair - Cost estimation, risk matrices, scheduling, resource allocation, and supply chains, because a brilliant design that runs out of budget never gets built - Safety standards and licensing, told through the Challenger O-rings and the exploding boilers that produced the first pressure vessel code - Sustainable design, robotics, machine learning, bioengineering, and nanotechnology Written for: - Students deciding whether to study engineering - Technicians, managers, and writers who work with engineers and want to follow the conversation - Career changers looking at the field from outside - Curious readers who want to understand the built world around them Each chapter closes with review questions, and worked example answers sit in the back. A historical timeline traces the profession across roughly 4,600 years, starting with Imhotep and ending with modern accreditation. A glossary defines the working vocabulary in plain language, covering terms like dead load, single point of failure, and mean time between failures. A recommended reading list points you toward good next books on any topic that catches you. You finish with three things: - a map of how the disciplines fit together - the vocabulary to talk with engineers and understand the technology running your life, - and a problem-solving method that works just as well for planning a business or fixing a faucet.