In boxing terms, a tough-looking fighter who can't take a punch is said to have a "glass jaw," and so it is these days with targets of controversy. Down the rabbit hole of scandal, the weak are strong and the strong are weak. Just consider this slate of recent reputational body blows: Toyota, Susan G. Komen, Paula Deen, Tiger Woods, Joe Paterno, BP, the Duke Lacrosse players, Lance Armstrong, and Anthony Weiner. Glass Jaw is a manifesto for these times, written by crisis management veteran Eric Dezenhall, who has spent three decades dealing with some of the most intense controversies, both known and . . . handled with discretion. In the current digital age, the fundamental nature of controversy is viral, rendering once-mighty organizations and individuals powerless against scandal. In Glass Jaw, Dezenhall analyzes scandal and demystifies the paper tiger "spin" industry, offering lessons, corrective measures, and counterintuitive insights, such as: How there really is no "getting ahead" of a bad story (and other cliches from the media) The perils of navigating the "Fiasco Vortex" The art (and transaction) of the public apology Why a crisis is not an opportunity The Nixon Fallacy: if only he had just said "I screwed up," the whole thing would have gone away (not a chance) How you are the enemy: the self-sabotage of selfies, tweets, emailing before thinking, technology creep, the privacy vacuum, and the industrialization of leaking. From the boardroom to the parenting messaging board, scandals erupt every day. Glass Jaw explains this changing nature of controversy and offers readers counterpunches to best protect themselves.

    With full coverage of 100% of exam objectives, this invaluable guide reinforces what you know, teaches you what you don't know, and gives you the hands-on practice you need to boost your skills. Written by expert Java developers, this book goes beyond mere exam prep with the insight, explanations and perspectives that come from years of experience. You'll review the basics of object-oriented programming, understand functional programming, apply your knowledge to database work, and much more. From the basic to the advanced, this guide walks you through everything you need to know to confidently take the OCP 1Z0-809 Exam and upgrade exams 1Z0-810 and 1Z0-813.Java 8 represents the biggest changes to the language to date, and the latest exam now requires that you demonstrate functional programming competence in order to pass. This guide has you covered, with clear explanations and expert advice.Understand abstract classes, interfaces, and class design Learn object-oriented design principles and patterns Delve into functional programming, advanced strings, and localization Master IO, NIO, and JDBC with expert-led database practice If you're ready to take the next step in your IT career, OCP: Oracle Certified Professional Java SE 8 Programmer II Study Guide is your ideal companion on the road to certification.

    Salesforce.com (more than 50%) and Twitter (more than 75% fall into this category. Ebay gets more than 8 billion API calls a month. Facebook and Google, have dozens of APIs that enable both free services and e-commerce, get more than 5 billion API calls each day. Other companies like NetFlix have expanded their service of streaming movies over the the web to dozens of devices using API. At peak times, more than 20 percent of all traffic is accounted for by Netflix through its APIs. Companies like Sears and E-Trade are opening up their catalogs and other services to allow developers and entrepreneurs to create new marketing experiences. Making an API work to create a new channel is not just a matter of technology. An API must be considered in terms of business strategy, marketing, and operations as well as the technical aspects of programming. This book, written by Greg Brail, CTO of Apigee, and Brian Mulloy, VP of Products, captures the knowledge of all these areas gained by Apigee, the leading company in supporting the rollout of high traffic APIs.

    When inexperienced entrepreneurs ask my advice about their idea for a tech startup, they often worry "What if Google decides to compete with us? They will crush us!" I respond that far more startups die of suicide than homicide. If you can avoid hurting yourself, then you are already better off than most of your competitors. Startups are a chance to build something entirely original with brilliant and ambitious people. But startups are also dangerous. Limited money means there is little room for mistakes. One bad decision can mean bankruptcy. The potential payoff attracts capital, which in turn attracts scam artists. The unscrupulous often lack the skills needed to succeed, but sometimes they are smart enough to trick investors. Even entrepreneurs who start with a strong moral compass can find that the threat of failure unmoors their ethics from their ambition. Emotions matter. We might hope that those in leadership positions possess strength and resilience, but vanity and fragile egos have sabotaged many of the businesses that I’ve worked with. Defeat is always a possibility, and not everyone finds healthy ways to deal with the stress. In this book I offer both advice and also warnings. I've seen certain self-destructive patterns play out again and again, so I wanted to document one of the most extreme cases that I've witnessed. In 2015 I worked for a startup that began with an ingenious idea: to use the software techniques known as Natural Language Processing to allow people to interact with databases by writing ordinary English sentences. This was a multi-billion dollar idea that could have transformed the way people gathered and used information. However, the venture had inexperienced leadership. They burned through their $1.3 million seed money. As their resources dwindled, their confidence transformed into doubt, which was aggravated by edicts from the Board Of Directors ordering sudden changes that effectively threw away weeks' worth of work. Every startup forces its participants into extreme positions, often regarding budget and deadlines. Often these situations are absurd to the point of parody. Therefore, there is considerable humor in this story. The collision of inexperience and desperation gives rise to moments that are simply silly. I tell this story in a day-to-day format, both to capture the early optimism, and then the later sense of panic. Here then, is a cautionary tale, a warning about tendencies that everyone joining a startup should be on guard against."

    As the size and complexity of commercial software have grown, the gap between academic computer science and industry has widened. It's an open secret that there is little engineering in software engineering, which continues to rely not on codified scientific knowledge but on intuition and experience.Barr, who worked as a programmer for more than twenty years, describes how the industry has evolved, from the era of mainframes and Fortran to today's embrace of the cloud. He explains bugs and why software has so many of them, and why today's interconnected computers offer fertile ground for viruses and worms. The difference between good and bad software can be a single line of code, and Barr includes code to illustrate the consequences of seemingly inconsequential choices by programmers. Looking to the future, Barr writes that the best prospect for improving software engineering is the move to the cloud. When software is a service and not a product, companies will have more incentive to make it good rather than "good enough to ship."

    Our eyes play tricks on us; our stories change in the retelling; and most of us are fairly sure we’re way above average. In Why We Make Mistakes, journalist Joseph T. Hallinan sets out to explore the science of human error—how we think, see, remember, and forget, and how this sets us up for wholly irresistible mistakes.In his quest to understand our imperfections, Hallinan delves into psychology, neuroscience, and economics, with forays into aviation, consumer behavior, geography, football, stock picking, and more. He discovers that some of the same qualities that make us efficient also make us error prone. Why We Make Mistakes is enlivened by real-life stories--of weathermen whose predictions are uncannily accurate and a witness who sent an innocent man to jail--and offers valuable advice, such as how to remember where you’ve hidden something important. He explains why multitasking is a bad idea, why men make errors women don’t. This book will open your eyes to the reasons behind your mistakes and have you vowing to do better the next time.

    Every officer should read and reread this text, to understand it, and to take its message to heart. Warfighting has stimulated discussion and debate from classrooms to wardooms, training areas to combat zones. The philosophy contained in this publication has influenced our approach to every task we have undertaken.

    It combines the productivity and expressivity of Ruby with the concurrency and fault-tolerance of Erlang. Elixir makes full use of Erlang's powerful OTP library, which many developers consider the source of Erlang's greatness, so you can have mature, professional-quality functionality right out of the gate. Elixir's support for functional programming makes it a great choice for highly distributed event-driven applications like IoT systems.The Little Elixir & OTP Guidebook gets you started programming applications with Elixir and OTP. You begin with a quick overview of the Elixir language syntax, along with just enough functional programming to use it effectively. Then, you'll dive straight into OTP and learn how it helps you build scalable, fault-tolerant and distributed applications through several fun examples. Come rediscover the joy of programming with Elixir and remember how it feels like to be a beginner again.

    You’ll quickly discover the many advantages of the language, including access to all the great tools and libraries of the .NET platform.Reap the benefits of functional programming for your next project, whether you’re writing concurrent code, or building data- or math-intensive applications. With this comprehensive book, former F# team member Chris Smith gives you a head start on the fundamentals and walks you through advanced concepts of the F# language.Learn F#’s unique characteristics for building applicationsGain a solid understanding of F#’s core syntax, including object-oriented and imperative stylesMake your object-oriented code better by applying functional programming patternsUse advanced functional techniques, such as tail-recursion and computation expressionsTake advantage of multi-core processors with asynchronous workflows and parallel programmingUse new type providers for interacting with web services and information-rich environmentsLearn how well F# works as a scripting language

     The first snowman appeared just outside of Pepper’s retirement home with a woman’s brooch on it. When more snowmen start popping up all over town, with items from her neighbors, Pepper realizes Dream Cove has a secret snowman on its hands. Read along as Pepper and her best friend, Tessa, follow the snowman’s trail until it leads directly to the biggest snowman of all. Secret Snowman is a clean cozy mystery. Read it for free with Kindle Unlimited.

    He’s gorgeous, well-built, and more than confident that he knows exactly what life has in store for him. But when Dhara Swamy walks into his life, brilliant, beautiful, and just a little bit broken, everything he thought he knew turns upside down. Dhara is attacked in her own home by unseen powers, and her scientist mind won’t let her accept the fact that there’s something happening to her that the natural laws of the universe just can’t explain. Kean is well-versed in the supernatural, though, and he recognizes immediately that Dhara needs the kind of help that can’t be found in a lab, explained in a textbook, or theorized in a classroom. Book Two Moira Brennan’s beauty is as vivid as her flame-red hair and glowing dragon scales. Both are a badge of vibrancy and power that she wears proudly, and while she’s not one to start a fight, she won’t walk away from one either. As part of the Boston dragon clan, Moira spends her days imbedded in the secret supernatural world of Boston, and her nights in her true dragon form, flying over the city, diving beneath the ocean, and resting in the tree tops. She’s not interested in settling down or changing anything about her life, but then Grady Princeton walks in a with a problem in his company’s vault and everything turns on its head. Book Three Eaman Cleary is a man of few words, and a bit of a mystery, even to those closest to him. He likes it that way, and he’s happiest when he’s flying through the air, his pure-white dragon form blending into the clouds and the pale-blue sky. White-blonde hair and artic skin only add to his mysterious persona, and nobody has ever inspired him to come out of his shell—at least not until Autumn Pruitt walks into the office, afraid for her own life and her daughters’ lives. Autumn never meant to stumble into the clearing in the woods or to see what she saw, but now she can’t get away from the consequences. Book Four Nothing scares Siobhan MacFaddan, except, perhaps, the fear that she’ll spend her life alone. Tall, tan, and blonde, she certainly gets plenty of attention, but she only wants attention from the man who is supposed to be her soulmate, if she can ever find him. Siobhan may not be exactly sure what she’s looking for in a soulmate, but she certainly knows what she’s not looking for, and that’s Julius Giordano, no matter how drop-dead gorgeous he is. When Julius comes to her office to tell her that he’s having visions where a man murders a woman, it doesn’t take her long to figure out that he has a supernatural window into the future or that the man gets under her skin—and not in a good way. But she has to save the woman in Julius’ visions, and as the case progresses, so do her feelings for the man suddenly gifted with psychic abilities. Book Five Ronan Connolly isn’t just another dragon shifter—he’s the rugged, gorgeous, powerful leader of his generation and the person charged with the responsibility of making sure that the clan’s quickly dwindling numbers don’t spell destruction. Dragon shifters can only breed with other dragon shifters, as the legend tells it, and that means that here is a growing shortage of mates for Ronan and his friends. All he cares about is saving the clan from dying out, and the only way to do that is to find some way for shifters and humans to reproduce together.

    Whittaker defines both in-the-small techniques for individual testers and in-the-large techniques to supercharge test teams. He also introduces a hybrid strategy for injecting exploratory concepts into traditional scripted testing. You'll learn when to use each, and how to use them all successfully.Concise, entertaining, and actionable, this book introduces robust techniques that have been used extensively by real testers on shipping software, illuminating their actual experiences with these techniques, and the results they've achieved. Writing for testers, QA specialists, developers, program managers, and architects alike, Whittaker answers crucial questions such as:- Why do some bugs remain invisible to automated testing--and how can I uncover them?- What techniques will help me consistently discover and eliminate "show stopper" bugs?- How do I make manual testing more effective--and less boring and unpleasant?- What's the most effective high-level test strategy for each project?- Which inputs should I test when I can't test them all?- Which test cases will provide the best feature coverage?- How can I get better results by combining exploratory testing with traditional script or scenario-based testing?- How do I reflect feedback from the development process, such as code changes?

    Full of energy and gusto, the novel takes you on an exploration of her inner thoughts as she deals with some of the government's 'finest.'

    This book demonstrates how the notation and process complement one another, using UML models to illustrate the new process in action. It describes the constructs such as use cases, actors, and more.

    Instead, The 12 Week Year avoids the pitfalls and low productivity of annualized thinking. This book redefines your "year" to be 12 weeks long. In 12 weeks, there just isn't enough time to get complacent, and urgency increases and intensifies. The 12 Week Year creates focus and clarity on what matters most and a sense of urgency to do it now. In the end more of the important stuff gets done and the impact on results is profound.Explains how to leverage the power of a 12-week year to drive improved results in any area of your lifeOffers a how-to book for both individuals and organizations seeking to improve their execution effectivenessAuthors are leading experts on execution and implementation Turn your organization's idea of a year on its head, and speed your journey to success.©2013 Brian P. Moran and Michael Lennington (P)2014 Audible Inc.