Successful Engineer

The battle with the Iron Legion has left The Last Horizon battered and broken, drifting in space. Varic needs an exceptional engineer to fix his ship, and there’s only one person for the job: Mell, the master Aether technician. But first, they have to break her out of prison. Mell has been captured by the Advocates, a group of superpowered vigilantes who dominate their corner of the galaxy. They are led by Starhammer, an invincible champion with a personal obsession with Mell.

How did a simple design error cause one of the great disasters of the 1980s - the collapse of the walkways at the Kansas City Hyatt Regency Hotel? What made the graceful and innovative Tacoma Narrows Bridge twist apart in a mild wind in 1940? How did an oversized waterlily inspire the magnificent Crystal Palace, the crowning achievement of Victorian architecture and engineering? These are some of the failures and successes that Henry Petroski, author of the acclaimed The Pencil, examines in this engaging, wonderfully literate book.

High performance expert Paul Rulkens provides the inside advice you need to accelerate your career as a business leader with an engineering background - from building on your unique strengths to achieving big business goals. How Successful Engineers Become Great Business Leaders is full of thought-provoking insights, practical applications, and pragmatic techniques to help you get everything you can out of everything you have.

At most technology companies, you'll reach Senior software engineer, the career level for software engineers, in five to eight years. At the career level, your company's career ladder won't require that you work towards the next promotion; being promoted further is an exception rather than expected. This is also when many engineers are first given an opportunity to move into engineering management.

For years, companies have rewarded their most effective engineers with management positions. But treating management as the default path for an engineer with leadership ability doesn't serve the industry well—or the engineer. The staff engineer's path allows engineers to contribute at a high level as role models, driving big projects, determining technical strategy, and raising everyone's skills. This in-depth book shows you how to understand your role, manage your time, master strategic thinking, and set the standard for technical work.

Emily's fight for women's suffrage is put on hold and her life transformed when Wash, the chief engineer of the Brooklyn Bridge, is injured on the job. Untrained for the task, but under his guidance, she assumes his role, despite stern resistance and overwhelming obstacles. Lines blur as Wash's vision becomes her own, and when he is unable to return to the job, Emily is consumed by it. But as the project takes shape under Emily's direction, she wonders whose legacy she is building - hers or her husband's.  

1881 - Special Agent Gillian Hamilton is a magic caster with the Federal Bureau of Magic and Steam. He’s sent to Shallow Grave, Arizona, to arrest a madman engineer known as Tinkerer, who’s responsible for blowing up half of Baltimore. Gillian has handled some of the worst criminals in the Bureau’s history, so this assignment shouldn’t be a problem. But even he’s taken aback by a run-in with the country’s most infamous outlaw, Gunner the Deadly.

Vince and his co-workers were waiting to catch a plane back from their business trip when aliens turned Earth into the setting for a deadly reality show.

The vast majority of writers begin the storytelling process with only a partial understanding of 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....

Described as the "ultimate engineer" during his career at NASA, George M. Low was a visionary architect and leader from the agency's inception in 1958 to his retirement in 1976. As chief of manned spaceflight at NASA, Low was instrumental in the Mercury, Gemini, and Apollo programs. Low's pioneering work paved the way for President Kennedy's decision to make a lunar landing NASA's primary goal in the 1960s.  

It’s been over a year since The Day. Morgan and his companions have fought to stay alive and he finally managed to get to his parents and bring them back. Their situation is getting better every day, but there are still challenges ahead of them. With a desire to return to a normal life on everyone’s mind, the group starts taking steps to do just that. Thinking bigger they tackle some major projects that will provide valuable resources. However, there are others out there making plans for them as well.

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. 

In Modern Software Engineering, continuous delivery pioneer David Farley helps software professionals think about their work more effectively, manage it more successfully, and genuinely improve the quality of their applications, their lives, and the lives of their colleagues.

In this book, author Will Larson shows you ways to obtain your first executive job and quickly ramp up to meet the challenges you may not have encountered in non-executive roles: measuring engineering for both engineers and the CEO, company-scoped headcount planning, communicating successfully across a growing organization, and figuring out what people actually mean when they keep asking for a "technology strategy."

Belfast, 1914. Two years after the sinking of the Titanic, high society has become obsessed with spiritualism, attending séances in the hope they might reach their departed loved ones. William Jackson Crawford is a man of science and a sceptic, but one night with everyone sitting around the circle, voices come to him – seemingly from beyond the veil – placing doubt in his heart and a seed of obsession in his mind. Could the spirits truly be communicating with him or is this one of Kathleen's parlour tricks gone too far?

The audiobook is focused on providing the listeners with a precise and concise understanding of what agile methodology is, how software testing is done under it and the key points by which a software professional can succeed in such work environments. As the goal of this audiobook is to quickly provide information to the listeners about the respective topics covered, the very intrinsic details of the respective topics are only covered to some extent.

Innovate or die For thirty years, Gary Shapiro has observed the world's most innovative businesses from his front-row seat as leader of the Consumer Electronics Association. Now he reveals the ten secrets of "ninja innovators" like Apple, Amazon, Google, Microsoft, and many others. What does it...