Now, along with award-winning novelist John Barnes, Aldrin offers a compelling novel about the opportunities and dangers that confront us in space today. Minute by minute, the International Space Station gets closer to tumbling out of orbit. Only former astronaut Scott Blackstone and his network of allies, fueled by their strong senses of idealism, can mount a rescue of the Station, and of the space program itself.

    Emphasizes possible, realistic and "best practice" approaches for managers, technical leads and self-managed teams. The author emphasizes efficient development concepts with an examination of rapid development strategies and a study of classic mistakes, within the context of software-development fundamentals and risk management. Dissects the core issues of rapid development, lifecycle planning, estimation and scheduling. Contains very good and practical discussions of customer-oriented development, motivation and teamwork. Explains such fundamental requirements as team structure, feature-set control (the dreaded feature creep in every project), availability and use of productivity tools and project recovery options. Relevant case studies are analyzed and discussed within the context of specific software development problems. Over 200 pages in this publication are devoted to a summary of best practices, everything from the daily build and smoke test, through prototyping, model selection, measurement, reuse, and the top-10 risks list. This publication is definitely recommended and will become a classic in the field, just as the author's prior publication, "Code Complete" already is.

    Feist's Riftwar Saga is the setting of the tale of "The Wood Boy."

    Never before told, behind the scenes stories mixed with humor and fascinating facts, plus a whopping 24 pages of great photos make this book a must read for Cubs fans. The remembrances are all here, told by an all-star team of people. It is like sitting around Wrigley Field listening to Ron's friends reminiscing about the man we all loved. Ron Santo Jr., contributed the Foreword.

    Frustrated by the lack of well-written essays on software engineering, Joel Spolsky (of www.joelonsoftware.com fame) has put together a collection of his favorite writings on the topic.With a nod to both the serious and funny sides of technical writing, The Best Software Writing I: Selected and Introduced by Joel Spolsky is an entertaining read and a guide to the technical writing literati.The Best Software Writing I contains writings from:Ken Arnold Leon Bambrick Michael Bean Rory Blyth Adam Bosworth danah boyd Raymond Chen Kevin Cheng and Tom Chi Cory Doctorow ea_spouse Bruce Eckel Paul Ford Paul Graham John Gruber Gregor Hohpe Ron Jeffries Eric Johnson Eric Lippert Michael Lopp Larry Osterman Mary Poppendieck Rick Schaut Aaron Swartz Clay Shirky Eric Sink why the lucky stiff

    There will be a lot of times when you need to get something done in Lightroom, but you have no idea where Adobe hid that feature, or what the “secret handshake” is to do that thing you need now so you can get back to working on your images. That’s why this book was created: to get you to the technique, the shortcut, or exactly the right setting, right now. Here’s how it works: When you need to know how to do a particular thing, you turn to the chapter where it would be found (Print, Slideshow, Organizing, Importing, etc.), find the thing you need to do (it’s easy-each page covers just one single topic), and Scott tells you exactly how to do it just like he was sitting there beside you, using the same casual style as if he were telling a friend. That way, you get back to editing your images fast.This isn’t a book of theory, full of confusing jargon and detailed multi-step concepts. This is a book on which button to click, which setting to use, and exactly how and when to use it, so you’re never “stuck” in Lightroom again. This will be your “go to” book that sits within reach any time you’re working in Lightroom, and you are going to love having this type of help right at your fingertips.

    It is difficult to imagine a world without instant access and 24/7 connectivity. We have reengineered our business, governance, and social relations around a planetary network unlike any that has come before. And, as with any social transformation, there have been unintended consequences.     In Black Code, Ron Deibert examines the profound effect that cyberspace is having on the relationship between citizens and states, on the private and public spheres, and on domestic and international affairs. Cyberspace has brought us a world of do-it-yourself signals intelligence, he argues, and WikiLeaks is only a symptom of a much larger phenomenon to which governments, businesses, and individuals will have to get accustomed. Our lives have been turned inside out by a digital world of our own spinning.     Fast-paced, revealing, and sometimes terrifying, Black Code takes readers into the shadowy realm of cybersecurity, offering insight into the very future of cyberspace and revealing what new rules and norms we will need to adopt in order to survive in this new environment.

    But the state-of-the-art has moved forward dramatically since Meyers last updated this book in 1997. (For instance, there s now STL. Design patterns. Even new functionality being added through TR1 and Boost.) So Meyers has done a top-to-bottom rewrite, identifying the 55 most valuable techniques you need now to be exceptionally effective with C++. Over half of this edition s content is new. Templates broadly impact C++ development, and you ll find them everywhere. There s extensive coverage of multithreaded systems. There s an entirely new chapter on resource management. You ll find substantial new coverage of exceptions. Much is gained, but nothing s lost: You ll find the same depth of practical insight that first made Effective C++ a classic all those years ago. Bill Camarda, from the July 2005 href="http://www.barnesandnoble.com/newslet... Only

    In his darkest moments, when those dreams were dashed, he dug deep with the help of an unlikely friend—five-year-old Maddux Maple, a local hometown fan with leukemia. They made a pact: Cody would be in the UFC and win the championship, and Maddux would beat cancer. Read their moving story in Cody’s new book, The Pact, and go behind the scenes into Cody’s training and how he made his dreams come true. Cody Garbrandt grew up in a rough town in the Central Appalachian region of Ohio, surrounded by a longstanding culture of fighting—and drugs. Raised in this environment by a single mom (his dad left him at the young age of three to reside in the Ohio State Penitentiary), Cody grew up fighting, and he grew up wild. His future seemed predestined to end in the coal mines, or in prison.Thankfully, Cody had visions of something more. His American Dream? Mixed Martial Arts. But a path to success wasn’t clear. He spent as much time fighting in the streets as he did in the gym—one bad decision away from losing everything. Then, at age 20, Cody’s brother introduced him to five-year old Maddux Maple. Maddux was deathly ill with leukemia, his survival by no means assured. A unique friendship developed as they made a promise to each other: Maddux would beat cancer, and Cody would make it to the UFC and become world champion.Through five long years of pain and hardship, they both persevered; Cody, through the agony and sacrifices of fighting his way to the top, and Maddux through the horrors of chemotherapy. They loved and supported each other. They served as each other’s inspiration. And in December 2016, they made good on their pact: Cody won his UFC Championship belt, which he promptly presented to Maddux—the boy who had beaten cancer into remission.

    D.S. Malik is ideal for a one-semester course focused on data structures. Clearly written with the student in mind, this text focuses on Data Structures and includes advanced topics in C++ such as Linked Lists and the Standard Template Library (STL). This student-friendly text features abundant Programming Examples and extensive use of visual diagrams to reinforce difficult topics. Students will find Dr. Malik's use of complete programming code and clear display of syntax, explanation, and example easy to read and conducive to learning.

    It is the definitive reference guide, now in a second edition. Although the first edition was written in 1978, it continues to be a worldwide best-seller. This second edition brings the classic original up to date to include the ANSI standard. From the Preface: We have tried to retain the brevity of the first edition. C is not a big language, and it is not well served by a big book. We have improved the exposition of critical features, such as pointers, that are central to C programming. We have refined the original examples, and have added new examples in several chapters. For instance, the treatment of complicated declarations is augmented by programs that convert declarations into words and vice versa. As before, all examples have been tested directly from the text, which is in machine-readable form. As we said in the first preface to the first edition, C "wears well as one's experience with it grows." With a decade more experience, we still feel that way. We hope that this book will help you to learn C and use it well.

    This work provides instructions, scripts, and tips to guide readers for grounding with discussions of the scripting language (PHP) and then the database program (MySQL).

    Whether they bind computers, economies, or terrorist organizations, networks are everywhere in the real world, yet only recently have scientists attempted to explain their mysterious workings.From epidemics of disease to outbreaks of market madness, from people searching for information to firms surviving crisis and change, from the structure of personal relationships to the technological and social choices of entire societies, Watts weaves together a network of discoveries across an array of disciplines to tell the story of an explosive new field of knowledge, the people who are building it, and his own peculiar path in forging this new science.

    WIth access to every computer in post-World War III's fully-automated society, he had the potential to become the ultimate spy, the perfect assassin, an invincible dictator.Only loyalty to samurai virtues kept his attention in check--until the day when Elizabeth was taken away from him, and Tokugawa began his quest for revenge...

    They aren't conscious of all the choices they make, like how they format their source, the names they use for variables, or the kinds of loops they use. They're focused entirely on problems they're solving, solutions they're creating, and algorithms they're implementing. So they write code in the way that seems natural, that happens intuitively, and that feels good.But if you're serious about your profession, intuition isn't enough. Perl Best Practices author Damian Conway explains that rules, conventions, standards, and practices not only help programmers communicate and coordinate with one another, they also provide a reliable framework for thinking about problems, and a common language for expressing solutions. This is especially critical in Perl, because the language is designed to offer many ways to accomplish the same task, and consequently it supports many incompatible dialects.With a good dose of Aussie humor, Dr. Conway (familiar to many in the Perl community) offers 256 guidelines on the art of coding to help you write better Perl code--in fact, the best Perl code you possibly can. The guidelines cover code layout, naming conventions, choice of data and control structures, program decomposition, interface design and implementation, modularity, object orientation, error handling, testing, and debugging.They're designed to work together to produce code that is clear, robust, efficient, maintainable, and concise, but Dr. Conway doesn't pretend that this is the one true universal and unequivocal set of best practices. Instead, Perl Best Practices offers coherent and widely applicable suggestions based on real-world experience of how code is actually written, rather than on someone's ivory-tower theories on how software ought to be created.Most of all, Perl Best Practices offers guidelines that actually work, and that many developers around the world are already using. Much like Perl itself, these guidelines are about helping you to get your job done, without getting in the way.Praise for Perl Best Practices from Perl community members:"As a manager of a large Perl project, I'd ensure that every member of my team has a copy of Perl Best Practices on their desk, and use it as the basis for an in-house style guide." -- Randal Schwartz"There are no more excuses for writing bad Perl programs. All levels of Perl programmer will be more productive after reading this book." -- Peter Scott"Perl Best Practices will be the next big important book in the evolution of Perl. The ideas and practices Damian lays down will help bring Perl out from under the embarrassing heading of "scripting languages". Many of us have known Perl is a real programming language, worthy of all the tasks normally delegated to Java and C++. With Perl Best Practices, Damian shows specifically how and why, so everyone else can see, too." -- Andy Lester"Damian's done what many thought impossible: show how to build large, maintainable Perl applications, while still letting Perl be the powerful, expressive language that programmers have loved for years." -- Bill Odom"Finally, a means to bring lasting order to the process and product of real Perl development teams." -- Andrew Sundstrom"Perl Best Practices provides a valuable education in how to write robust, maintainable P