One slogan of Perl is that it makes easy things easy and hard things possible. "Intermediate Perl" is about making the leap from the easy things to the hard ones.Originally released in 2003 as "Learning Perl Objects, References, and Modules" and revised and updated for Perl 5.8, this book offers a gentle but thorough introduction to intermediate programming in Perl. Written by the authors of the best-selling "Learning Perl," it picks up where that book left off. Topics include: Packages and namespacesReferences and scopingManipulating complex data structuresObject-oriented programmingWriting and using modulesTesting Perl codeContributing to CPANFollowing the successful format of "Learning Perl," we designed each chapter in the book to be small enough to be read in just an hour or two, ending with a series of exercises to help you practice what you've learned. To use the book, you just need to be familiar with the material in "Learning Perl" and have ambition to go further.Perl is a different language to different people. It is a quick scripting tool for some, and a fully-featured object-oriented language for others. It is used for everything from performing quick global replacements on text files, to crunching huge, complex sets of scientific data that take weeks to process. Perl is what you make of it. But regardless of what you use Perl for, this book helps you do it more effectively, efficiently, and elegantly."Intermediate Perl" is about learning to use Perl as a programming language, and not just a scripting language. This is the book that turns the Perl dabbler into the Perl programmer.

    For this special hardcover edition, two new appendixes on locales and standard library exception safety (also available at www.research.att.com/ bs/) have been added. The result is complete, authoritative coverage of the C++ language, its standard library, and key design techniques. Based on the ANSI/ISO C++ standard, The C++ Programming Language provides current and comprehensive coverage of all C++ language features and standard library components. For example:abstract classes as interfaces class hierarchies for object-oriented programming templates as the basis for type-safe generic software exceptions for regular error handling namespaces for modularity in large-scale software run-time type identification for loosely coupled systems the C subset of C++ for C compatibility and system-level work standard containers and algorithms standard strings, I/O streams, and numerics C compatibility, internationalization, and exception safety Bjarne Stroustrup makes C++ even more accessible to those new to the language, while adding advanced information and techniques that even expert C++ programmers will find invaluable.

    “The result is a veritable pi

    But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way. Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship . Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code on the fly into a book that will instill within you the values of a software craftsman and make you a better programmer but only if you work at it. What kind of work will you be doing? You'll be reading code - lots of code. And you will be challenged to think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft. Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code - of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code. Readers will come away from this book understanding ‣ How to tell the difference between good and bad code‣ How to write good code and how to transform bad code into good code‣ How to create good names, good functions, good objects, and good classes‣ How to format code for maximum readability ‣ How to implement complete error handling without obscuring code logic ‣ How to unit test and practice test-driven development This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

    There she saw first-hand how deeply intertwined Silicon Valley was with the federal government, and always had been, and how shallow the common understanding of the secrets of the Valley's success actually was. Now, after almost five years of pioneering research, O'Mara has produced the definitive history of Silicon Valley for our time, the story of mavericks and visionaries, but also of powerful institutions creating the framework for innovation, from the Pentagon to Stanford University. It is also a story of a community that started off remarkably homogeneous and elitist and stayed that way, and whose belief in its own mythology has deepened into a collective hubris that has led to astonishing triumphs as well as devastating second-order effects.Deploying a wonderfully rich and diverse cast of protagonists, from the justly famous to the unjustly obscure, across four generations of explosive growth in the Valley, from the Forties to the present, O'Mara has wrestled into magnificent narrative form one of the most fateful developments in modern American history. She is on the ground with all of the key tech companies, and chronicles the evolution in their offerings through each successive era, and she has a profound fingertip feel for the politics of the sector, and its relation to the larger cultural narrative about tech as it has evolved over the years. Perhaps most impressively, O'Mara has penetrated the inner kingdom of tech venture capital firms, the insular and still remarkably old-boy world that became the cockpit of American capitalism and the crucible for bringing technological innovation to market, or not. The transformation of big tech into the engine room of the American economy and the nexus of so many of our hopes and dreams--and increasingly nightmares--can be understood, in Margaret O'Mara's masterful hands, as the story of one California valley. As her majestic history makes clear, its fate is the fate of us all.

    Since 2001, newspaper and music revenues have fallen by 70%, book publishing, film and television profits have also fallen dramatically. Revenues at Google in this same period grew from $400 million to $74.5 billion. Google's YouTube today controls 60% of the streaming audio business and pays only 11% of the streaming audio revenues. More creative content is being consumed than ever before, but less revenue is flowing to creators and owners of the content.With the reallocation of money to monopoly platforms comes a shift in power. Google, Facebook, and Amazon now enjoy political power on par with Big Oil and Big Pharma, which in part explains how such a tremendous shift in revenues from artists to platforms could have been achieved and why it has gone unchallenged for so long.The stakes in this story go far beyond the livelihood of any one musician or journalist. As Taplin observes, the fact that more and more Americans receive their news, music and other forms of entertainment from a small group of companies poses a real threat to democracy. Move Fast and Break Things offers a vital, forward-thinking prescription for how artists can reclaim their audiences using knowledge of the past and a determination to work together. Using his own half-century career as a music and film producer and early pioneer of streaming video online, Taplin offers new ways to think about the design of the World Wide Web and specifically the way we live with the firms that dominate it.Table of contentsIntroduction1. The Great Disruption2. Levon's Story3. Tech's Counterculture Roots4. The Libertarian Counterinsurgency5. Digital Destruction6. Monopoly in the Digital Age7. Google's Regulatory Capture8. The Social Media Revolution9. Pirates of the Internet10. Libertarian and the 1 Percent11. What It Means to Be Human12. The Digital RenaissanceAfterword

    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.

    It took the open source world by storm since its inception in 2005, and is used by small development shops and giants like Google, Red Hat, and IBM, and of course many open source projects.A book by Git experts to turn you into a Git expert. Introduces the world of distributed version control Shows how to build a Git development workflow.

    But with a typical price tag of $5,000 to $10,000 for a usability consultant to conduct each round of tests, it rarely happens. In this how-to companion to Don't Make Me Think: A Common Sense Approach to Web Usability, Steve Krug spells out an approach to usability testing that anyone can easily apply to their own web site, application, or other product. (As he said in Don't Make Me Think, "It's not rocket surgery".)In this new book, Steve explains how to: -Test any design, from a sketch on a napkin to a fully-functioning web site or application-Keep your focus on finding the most important problems (because no one has the time or resources to fix them all)-Fix the problems that you find, using his "The least you can do" approachBy pairing the process of testing and fixing products down to its essentials (A morning a month, that's all we ask ), Rocket Surgery makes it realistic for teams to test early and often, catching problems while it's still easy to fix them. Rocket Surgery Made Easy adds demonstration videos to the proven mix of clear writing, before-and-after examples, witty illustrations, and practical advice that made Don't Make Me Think so popular.

    Part entrepreneur, part enfant terrible, Gates has become the most powerful -- and feared -- player in the computer industry, and arguably the richest man in America. In Hard Drive, investigative reporters Wallace and Erickson follow Gates from his days as an unkempt thirteen-year-old computer hacker to his present-day status as a ruthless billionaire CEO. More than simply a "revenge of the nerds" story though, this is a balanced analysis of a business triumph, and a stunningly driven personality. The authors have spoken to everyone who knows anything about Bill Gates and Microsoft -- from childhood friends to employees and business rivals who reveal the heights, and limits, of his wizardry. From Gates's singular accomplishments to his equally extraordinary brattiness, arrogance, and hostility (the atmosphere is so intense at Microsoft that stressed-out programmers have been known to ease the tension of their eighty-hour workweeks by exploding homemade bombs), this is a uniquely revealing glimpse of the person who has emerged as the undisputed king of a notoriously brutal industry.

    At the same time, Steve Jobs was being forced out of his beloved Apple and starting over with a new company, NeXT Computer. His goal was to build a supercomputer with the power to transform education. Menuez had found his story: he proposed to photograph Jobs and his extraordinary team as they built this new computer, from conception to product launch. In an amazing act of trust, Jobs granted Menuez unlimited access to the company, and, for the next three years, Menuez was able to get on film the spirit and substance of innovation through the day-to-day actions of the world’s top technology guru. From there, the project expanded to include the most trailblazing companies in Silicon Valley, all of which granted Menuez the same complete access that Jobs had. Menuez photographed behind the scenes with John Warnock at Adobe, John Sculley at Apple, Bill Gates at Microsoft, John Doerr at Kleiner Perkins, Bill Joy at Sun Microsystems, Gordon Moore and Andy Grove at Intel, Marc Andreessen at Netscape, and more than seventy other leading companies and innovators. It would be fifteen years before Menuez stopped taking pictures, just as the dotcom bubble burst. An extraordinary era was coming to its close. With his singular behind-the-scenes access to these notoriously insular companies, Menuez was present for moments of heartbreaking failure and unexpected success, moments that made history, and moments that revealed the everyday lives of the individuals who made it happen. This period of rapid, radical change would affect almost every aspect of our culture and our lives in ways both large and small and would also create more jobs and wealth than any other time in human history. And Doug Menuez was there, a witness to a revolution. In more than a hundred photographs and accompanying commentary, Fearless Genius captures the human face of innovation and shows what it takes to transform powerful ideas into reality.

     While very complex, the Internet operates on a few relatively simple concepts that anyone can understand. Networks and networked applications are embedded in our lives. Understanding how these technologies work is invaluable.  This book was written for everyone - no technical knowledge is required!While this book is not specifically about the Network+ or CCNA certifications, it as a way to give students interested in these certifications a starting point.

    But developing these systems brings its own set of headaches. With lots of examples and practical advice, this book takes a holistic view of the topics that system architects and administrators must consider when building, managing, and evolving microservice architectures.Microservice technologies are moving quickly. Author Sam Newman provides you with a firm grounding in the concepts while diving into current solutions for modeling, integrating, testing, deploying, and monitoring your own autonomous services. You'll follow a fictional company throughout the book to learn how building a microservice architecture affects a single domain.Discover how microservices allow you to align your system design with your organization's goalsLearn options for integrating a service with the rest of your systemTake an incremental approach when splitting monolithic codebasesDeploy individual microservices through continuous integrationExamine the complexities of testing and monitoring distributed servicesManage security with user-to-service and service-to-service modelsUnderstand the challenges of scaling microservice architectures

    Big Blue, as the company is known, tends to rely for its success on magical thinking but that magic ran out a long time ago. The company got in trouble back in the 1990s and had to hire for the first time an outside CEO, Lou Gerstner, to save the day. Gerstner pushed IBM into services with spectacular results but this hurt the company, too. As services have became commoditized IBM could only compete by offshoring the work and quality suffered. The other negative impact of Gerstner was his compensation which was for the first time in IBM history very high. Only the Watson family had become rich running IBM with later CEOs like John Opel and John Akers living comfortable lives with lots of perks, but they never got BIG RICH. That changed with Gerstner. Sam Palmisano an IBM lifer followed Gerstner as CEO and followed, too, the Gerstner playbook. Palmisano retired three years ago with a retirement package worth $241 million, replaced by IBM's first woman CEO, Ginni Rometty, who certainly expects a comparable golden parachute. In order to achieve these numbers, though, IBM has essentially sacrificed both its customers and employees. In order to have ever growing earnings per share the company has cut labor to the bone, off-shored everything it can, dropped quality, deliberately underbid contracts to win them then not performed. IBM's acquisition policy is one of buying companies to get their sales then cutting costs to the bone and under-delivering. This and share buybacks have kept earnings growing until this house of cards recently began to fall. Ginni Rometty, who will end up taking the fall for Palmisano's flawed strategy, has stated a very specific earnings goal for 2015 that she will destroy the company to achieve if she must. This book how IBM fell from grace, where it is headed, and what specifically can be done to save the company before it is too late.

    Written by the man who started the adventure, Behind Deep Blue reveals the inside story of what happened behind the scenes at the two historic Deep Blue vs. Kasparov matches. This is also the story behind the quest to create the mother of all chess machines. The book unveils how a modest student project eventually produced a multimillion dollar supercomputer, from the development of the scientific ideas through technical setbacks, rivalry in the race to develop the ultimate chess machine, and wild controversies to the final triumph over the world's greatest human player.In nontechnical, conversational prose, Feng-hsiung Hsu, the system architect of Deep Blue, tells us how he and a small team of fellow researchers forged ahead at IBM with a project they'd begun as students at Carnegie Mellon in the mid-1980s: the search for one of the oldest holy grails in artificial intelligence--a machine that could beat any human chess player in a bona fide match. Back in 1949 science had conceived the foundations of modern chess computers but not until almost fifty years later--until Deep Blue--would the quest be realized.Hsu refutes Kasparov's controversial claim that only human intervention could have allowed Deep Blue to make its decisive, "uncomputerlike" moves. In riveting detail he describes the heightening tension in this war of brains and nerves, the "smoldering fire" in Kasparov's eyes. Behind Deep Blue is not just another tale of man versus machine. This fascinating book tells us how man as genius was given an ultimate, unforgettable run for his mind, no, not by the genius of a computer, but of man as toolmaker.