The Story Of Engineering

What makes a good story or a screenplay great? The vast majority of writers begin the storytelling process with only a partial understanding where to begin. Some labor their entire lives without ever learning that successful stories are as dependent upon good engineering as they are artistry. But the truth is, unless you are master of the form, function and criteria of successful storytelling, sitting down and pounding out a first draft without planning is an ineffective way to begin. Story Engineering starts with the criteria and the architecture of storytelling, the engineering and design of a story--and uses it as the basis for narrative. The greatest potential of any story is found in the way six specific aspects of storytelling combine and empower each other on the page. When rendered artfully, they become a sum in excess of their parts. You'll learn to wrap your head around the big pictures of storytelling at a professional level through a new approach that shows how to combine these six core competencies which include: • Four elemental competencies of concept, character, theme, and story structure (plot) • Two executional competencies of scene construction and writing voice The true magic of storytelling happens when these six core competencies work together in perfect harmony. And the best part? Anyone can do it!

Eight Amazing Engineering Stories reveals the stories behind how engineers use specific elements to create the material world around us. In eight chapters, the EngineerGuy team exposes the magnificence of the innovation and engineering of digital camera imagers, tiny accelerometers, atomic clocks, enriched uranium, batteries, microwave ovens, lasers, and anodized metals. In addition, short primers cover the scientific principles underlying the engineering, including waves, nuclear structure, and electronic transitions. "In Depth" sections cover entropy, semiconductors, and the mathematics of capacitors. Eight Amazing Engineering Stories forms the basis of the fourth series of EngineerGuy videos found on-line.

This volume celebrates the can-do, risk-taking, creative pioneers of Texas Instruments from its inception in the 1930s as a tiny geophysical exploration company working out of the back of a truck in the oilfields of the Southwest, to its status in the world today as one of the world's leading electronics companies. From the determination of its founders--Eugene McDermott, Erik Jonsson, Cecil Green, and Pat Haggerty--to the genius of its inventors such as Nobel prizewinner Jack Kilby, TI has transformed the world in seven and a half decades. In photographs and anecdotes, the book tells TI's history of innovation in products and technologies, including the development of the first commercial silicon transistors, the first integrated circuits, and the first electronic hand-held calculators. Today, this Fortune 500 company is at the forefront of digital signal processing and analog technologies--the semiconductor engines of the Internet age. TIers are currently working on solutions for large global markets such as wireless and broadband access, and for a variety of emerging markets such as digital projection systems and digital audio. The seventy-five vignettes making up this history paint a picture of TI and its people, providing a window into a corporate culture that fosters the creativity and mental toughness to compete in the world semiconductor market. The stories, in addition, show TI's staunch sense of fiscal responsibility, civic mindedness, and high ethical standards in its business practices.

‘Engineering padicha nalla future – If you study engineering, you will have a good future.’ This is a claim often repeated to children and teenagers by parents and teachers in many parts of India. But only those who have gone through an engineering college life know that it’s not completely true. There is a difference between calling yourself as an engineering graduate and an engineer. India produces millions of engineering graduates like you and me but only very few of us are actual engineers. Many of us just graduate with an engineering degree, with an artistic dream in mind. What do you think is the difference between engineers in many countries around the world and engineers from India? In other countries, if David Pascal studied electrical engineering in college, few years later you can find him working as an electrical engineer. In India, if Ram Krishnamurthy studied electrical engineering, few years later you can find him working in a completely irrelevant field like software coding, banking, photography and even movie directing. This book is not about the few engineering students in your class who love engineering. I don’t hate them. In fact, I am very jealous that they study what they love. This book is about the majority of engineering graduates whose lives are wasted in engineering and is intended to tell you why you should make an attempt in pursuing your real passion, instead of being suffocated under the weight of an engineering degree. This is a story of India’s Youth. Welcome to India, the land of Wasted Engineers.

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

Providing unique, accessible lessons on engineering, this title in the bestselling 101 Things I Learned® series is a perfect resource for students, recent graduates, general readers, and even seasoned professionals. An experienced civil engineer presents the physics and fundamentals underlying the many fields of engineering. Far from a dry, nuts-and-bolts exposition, 101 Things I Learned® in Engineering School uses real-world examples to show how the engineer's way of thinking can illuminate questions from the simple to the profound: Why shouldn't soldiers march across a bridge? Why do buildings want to float and cars want to fly? What is the difference between thinking systemically and thinking systematically? This informative resource will appeal to students, general readers, and even experienced engineers, who will discover within many provocative insights into familiar principles.