It’s not about how smart you are, but how open you are to learn new and effective powerful conversational rituals that prime the brain for trust, partnership, and mutual success. Conversational Intelligence translates the wealth of new insights coming out of neuroscience from across the globe, and brings the science down to earth so people can understand and apply it in their everyday lives. Author Judith Glaser presents a framework for knowing what kind of conversations trigger the lower, more primitive brain; and what activates higher-level intelligences such as trust, integrity, empathy, and good judgment. Conversational Intelligence makes complex scientific material simple to understand and apply through a wealth of easy to use tools, examples, conversational rituals, and practices for all levels of an organization.

    An essential handbook on a favorite topic—love—it will help women understand the wider meaning of love as a tool, a resource, and a force. It encourages girls to love themselves first and then reflect on the significance of love outside the common perceptions of romantic love and its role in their friendships and the world at large. It is a road map for every woman to navigate long-distance relationships, determine the real Prince Charmings, overcome icon infatuations, rediscover childhood dreams, and rule in all affairs of the heart.

    This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers, and operations, delivery teams can get changes released in a matter of hours-- sometimes even minutes-no matter what the size of a project or the complexity of its code base. Jez Humble and David Farley begin by presenting the foundations of a rapid, reliable, low-risk delivery process. Next, they introduce the "deployment pipeline," an automated process for managing all changes, from check-in to release. Finally, they discuss the "ecosystem" needed to support continuous delivery, from infrastructure, data and configuration management to governance. The authors introduce state-of-the-art techniques, including automated infrastructure management and data migration, and the use of virtualization. For each, they review key issues, identify best practices, and demonstrate how to mitigate risks. Coverage includes - Automating all facets of building, integrating, testing, and deploying software - Implementing deployment pipelines at team and organizational levels - Improving collaboration between developers, testers, and operations - Developing features incrementally on large and distributed teams - Implementing an effective configuration management strategy - Automating acceptance testing, from analysis to implementation - Testing capacity and other non-functional requirements - Implementing continuous deployment and zero-downtime releases - Managing infrastructure, data, components and dependencies - Navigating risk management, compliance, and auditing Whether you're a developer, systems administrator, tester, or manager, this book will help your organization move from idea to release faster than ever--so you can deliver value to your business rapidly and reliably.

    When Irene was born, her parents were advised to institutionalize her. They refused and instead became trailblazers in advocating for the rights of people with mental disabilities. The entire family benefited, with a life rich in stress, sorrows, hilarity, joy, and overwhelming kindness from strangers. Terrell has found that the only way to get through the difficult moments is to laugh--even in the most trying of times. In her moving, funny, and unforgettable memoir about life with Irene, Terrell Dougan shows that love, humor, and compassion are enough to heal us, every single day.

    I'm going to share that mindset with you — along with hundreds of actionable techniques and proven habits — so you can shortcut those years.Introducing The Effective Engineer — the only book designed specifically for today's software engineers, based on extensive interviews with engineering leaders at top tech companies, and packed with hundreds of techniques to accelerate your career.For two years, I embarked on a quest seeking an answer to one question:How do the most effective engineers make their efforts, their teams, and their careers more successful?I interviewed and collected stories from engineering VPs, directors, managers, and other leaders at today's top software companies: established, household names like Google, Facebook, Twitter, and LinkedIn; rapidly growing mid-sized companies like Dropbox, Square, Box, Airbnb, and Etsy; and startups like Reddit, Stripe, Instagram, and Lyft.These leaders shared stories about the most valuable insights they've learned and the most common and costly mistakes that they've seen engineers — sometimes themselves — make.This is just a small sampling of the hard questions I posed to them:- What engineering qualities correlate with future success?- What have you done that has paid off the highest returns?- What separates the most effective engineers you've worked with from everyone else?- What's the most valuable lesson your team has learned in the past year?- What advice do you give to new engineers on your team? Everyone's story is different, but many of the lessons share common themes.You'll get to hear stories like:- How did Instagram's team of 5 engineers build and support a service that grew to over 40 million users by the time the company was acquired?- How and why did Quora deploy code to production 40 to 50 times per day?- How did the team behind Google Docs become the fastest acquisition to rewrite its software to run on Google's infrastructure?- How does Etsy use continuous experimentation to design features that are guaranteed to increase revenue at launch?- How did Facebook's small infrastructure team effectively operate thousands of database servers?- How did Dropbox go from barely hiring any new engineers to nearly tripling its team size year-over-year? What's more, I've distilled their stories into actionable habits and lessons that you can follow step-by-step to make your career and your team more successful.The skills used by effective engineers are all learnable.And I'll teach them to you. With The Effective Engineer, I'll teach you a unifying framework called leverage — the value produced per unit of time invested — that you can use to identify the activities that produce disproportionate results.Here's a sneak peek at some of the lessons you'll learn. You'll learn how to:- Prioritize the right projects and tasks to increase your impact.- Earn more leeway from your peers and managers on your projects.- Spend less time maintaining and fixing software and more time building and shipping new features.- Produce more accurate software estimates.- Validate your ideas cheaply to reduce wasted work.- Navigate organizational and people-related bottlenecks.- Find the appropriate level of code reviews, testing, abstraction, and technical debt to balance speed and quality.- Shorten your debugging workflow to increase your iteration speed.

    In this brutally honest and intimate memoir, Somers offers readers an inside view of a food addict’s mind, showcasing her experiences of obsessive cravings, compulsivity, and powerlessness regarding food.Saving Sara chronicles Somers’s addiction from childhood to adulthood, beginning with abnormal eating as a nine-year-old. As her addiction progresses in young adulthood, she becomes isolated, masking her shame and self-hatred with drugs and alcohol. Time and again, she rationalizes why this time will be different, only to have her physical cravings lead to ever-worse binges, to see her promises of doing things differently next time broken, and to experience the amnesia that she—like every addict—experiences when her obsession sets in again.Even after Somers is introduced to the solution that will eventually end up saving her, the strength of her addiction won’t allow her to accept her disease. Twenty-six more years pass until she finally crawls on hands and knees back to that solution, and learns to live life on life’s terms. A raw account of Somers’s decades-long journey, Saving Sara underscores the challenges faced by food addicts of any age—and the hope that exists for them all.

    In this book, you'll learn how to become an entrepreneur, driving your career in the direction of your choosing. You'll learn how to build your software development career step by step, following the same path that you would follow if you were building, marketing, and selling a product. After all, your skills themselves are a product. The choices you make about which technologies to focus on and which business domains to master have at least as much impact on your success as your technical knowledge itself--don't let those choices be accidental. We'll walk through all aspects of the decision-making process, so you can ensure that you're investing your time and energy in the right areas. You'll develop a structured plan for keeping your mind engaged and your skills fresh. You'll learn how to assess your skills in terms of where they fit on the value chain, driving you away from commodity skills and toward those that are in high demand. Through a mix of high-level, thought-provoking essays and tactical "Act on It" sections, you will come away with concrete plans you can put into action immediately. You'll also get a chance to read the perspectives of several highly successful members of our industry from a variety of career paths. As with any product or service, if nobody knows what you're selling, nobody will buy. We'll walk through the often-neglected world of marketing, and you'll create a plan to market yourself both inside your company and to the industry in general. Above all, you'll see how you can set the direction of your career, leading to a more fulfilling and remarkable professional life.

    So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems?In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient--lessons directly applicable to your organization.This book is divided into four sections: Introduction--Learn what site reliability engineering is and why it differs from conventional IT industry practicesPrinciples--Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE)Practices--Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systemsManagement--Explore Google's best practices for training, communication, and meetings that your organization can use

    It could forever change how you experience and interact with your physical surroundings, open your eyes to the perversity of bad design and the desirability of good design, and raise your expectations about how things should be designed.B & W photographs and illustrations throughout.

    This book draws on material Michael created for his renowned Object Mentor seminars, techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control. The topics covered include: Understanding the mechanics of software change, adding features, fixing bugs, improving design, optimizing performance Getting legacy code into a test harness Writing tests that protect you against introducing new problems Techniques that can be used with any language or platform, with examples in Java, C++, C, and C# Accurately identifying where code changes need to be made Coping with legacy systems that aren't object-oriented Handling applications that don't seem to have any structureThis book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.

    Now this same team provides the best explanation yet of these new features, and of concurrency in general. Concurrency is no longer a subject for advanced users only. Every Java developer should read this book."--Martin BuchholzJDK Concurrency Czar, Sun Microsystems"For the past 30 years, computer performance has been driven by Moore's Law; from now on, it will be driven by Amdahl's Law. Writing code that effectively exploits multiple processors can be very challenging. Java Concurrency in Practice provides you with the concepts and techniques needed to write safe and scalable Java programs for today's--and tomorrow's--systems."--Doron RajwanResearch Scientist, Intel Corp"This is the book you need if you're writing--or designing, or debugging, or maintaining, or contemplating--multithreaded Java programs. If you've ever had to synchronize a method and you weren't sure why, you owe it to yourself and your users to read this book, cover to cover."--Ted NewardAuthor of Effective Enterprise Java"Brian addresses the fundamental issues and complexities of concurrency with uncommon clarity. This book is a must-read for anyone who uses threads and cares about performance."--Kirk PepperdineCTO, JavaPerformanceTuning.com"This book covers a very deep and subtle topic in a very clear and concise way, making it the perfect Java Concurrency reference manual. Each page is filled with the problems (and solutions!) that programmers struggle with every day. Effectively exploiting concurrency is becoming more and more important now that Moore's Law is delivering more cores but not faster cores, and this book will show you how to do it."--Dr. Cliff ClickSenior Software Engineer, Azul Systems"I have a strong interest in concurrency, and have probably written more thread deadlocks and made more synchronization mistakes than most programmers. Brian's book is the most readable on the topic of threading and concurrency in Java, and deals with this difficult subject with a wonderful hands-on approach. This is a book I am recommending to all my readers of The Java Specialists' Newsletter, because it is interesting, useful, and relevant to the problems facing Java developers today."--Dr. Heinz KabutzThe Java Specialists' Newsletter"I've focused a career on simplifying simple problems, but this book ambitiously and effectively works to simplify a complex but critical subject: concurrency. Java Concurrency in Practice is revolutionary in its approach, smooth and easy in style, and timely in its delivery--it's destined to be a very important book."--Bruce TateAuthor of Beyond Java" Java Concurrency in Practice is an invaluable compilation of threading know-how for Java developers. I found reading this book intellectually exciting, in part because it is an excellent introduction to Java's concurrency API, but mostly because it captures in a thorough and accessible way expert knowledge on threading not easily found elsewhere."--Bill VennersAuthor of Inside the Java Virtual MachineThreads are a fundamental part of the Java platform. As multicore processors become the norm, using concurrency effectively becomes essential for building high-performance applications. Java SE 5 and 6 are a huge step forward for the development of concurrent applications, with improvements to the Java Virtual Machine to support high-performance, highly scalable concurrent classes and a rich set of new concurrency building blocks. In Java Concurrency in Practice , the creators of these new facilities explain not only how they work and how to use them, but also the motivation and design patterns behind them.However, developing, testing, and debugging multithreaded programs can still be very difficult; it is all too easy to create concurrent programs that appear to work, but fail when it matters most: in production, under heavy load. Java Concurrency in Practice arms readers with both the theoretical underpinnings and concrete techniques for building reliable, scalable, maintainable concurrent applications. Rather than simply offering an inventory of concurrency APIs and mechanisms, it provides design rules, patterns, and mental models that make it easier to build concurrent programs that are both correct and performant.This book covers:Basic concepts of concurrency and thread safety Techniques for building and composing thread-safe classes Using the concurrency building blocks in java.util.concurrent Performance optimization dos and don'ts Testing concurrent programs Advanced topics such as atomic variables, nonblocking algorithms, and the Java Memory Model

    Others have the knack of unerringly zeroing in on the root cause of a bug. Are they geniuses? Just lucky? No, they've learned the secrets of professional debugging. This book will equip you with the tools, techniques and approaches-proven in the crucible of professional software development-to ensure that you can tackle any bug with confidence. You'll learn how to handle every stage of the bug life-cycle, from constructing software that makes debugging easy, through detection, reproduction, diagnosis and rolling out your eventual fix. If you develop software, sooner or later you're going to discover that it doesn't always behave as you intended. Working out why it's misbehaving can be hard. Sometimes very hard. Debug It! is here to help! All bugs are different: there is no silver bullet. You've got to rely upon your intellect, intuition, detective skills and yes, even a little luck. But that doesn't mean that you're completely on your own-there is much you can learn from those who have gone before. This book distills decades of hard-won experience gained in the trenches of professional software development, giving you a head-start and arming you with the tools you need to get to the bottom of the problem, whatever you're faced with. Whether you're writing Java or assembly language, targeting servers or embedded micro-controllers, using agile or traditional approaches, the same basic bug-fixing principles apply. From constructing software that is easy to debug (and incidentally less likely to contain bugs in the first place), through handling bug reports to rolling out your ultimate fix, we'll cover the entire life-cycle of a bug. You'll learn about the empirical approach, which leverages your software's unique ability to show you what's really happening, the importance of finding a reliable and convenient means of reproducing a bug, and common pitfalls so you can avoid them. You'll see how to use commonly available tools to automatically detect problems before they're reported by customers and how to construct "transparent software" that provides access to critical information and internal state.

    But is it possible America's most troubling impact on the globalizing world has yet to be accounted for? In "Crazy Like Us," Ethan Watters reveals that the most devastating consequence of the spread of American culture has not been our golden arches or our bomb craters but our bulldozing of the human psyche itself: We are in the process of homogenizing the way the world goes mad. America has been the world leader in generating new mental health treatments and modern theories of the human psyche. We export our psychopharmaceuticals packaged with the certainty that our biomedical knowledge will relieve the suffering and stigma of mental illness. We categorize disorders, thereby defining mental illness and health, and then parade these seemingly scientific certainties in front of the world. The blowback from these efforts is just now coming to light: It turns out that we have not only been changing the way the world talks about and treats mental illness -- we have been changing the mental illnesses themselves.For millennia, local beliefs in different cultures have shaped the experience of mental illness into endless varieties." Crazy Like Us" documents how American interventions have discounted and worked to change those indigenous beliefs, often at a dizzying rate. Over the last decades, mental illnesses popularized in America have been spreading across the globe with the speed of contagious diseases. Watters travels from China to Tanzania to bring home the unsettling conclusion that the virus is us: As we introduce Americanized ways of treating mental illnesses, we are in fact spreading the diseases.In post-tsunami Sri Lanka, Watters reports on the Western trauma counselors who, in their rush to help, inadvertently trampled local expressions of grief, suffering, and healing. In Hong Kong, he retraces the last steps of the teenager whose death sparked an epidemic of the American version of anorexia nervosa. Watters reveals the truth about a multi-million-dollar campaign by one of the world's biggest drug companies to change the Japanese experience of depression -- literally marketing the disease along with the drug.But this book is not just about the damage we've caused in faraway places. Looking at our impact on the psyches of people in other cultures is a gut check, a way of forcing ourselves to take a fresh look at our own beliefs about mental health and healing. When we examine our assumptions from a farther shore, we begin to understand how our own culture constantly shapes and sometimes creates the mental illnesses of our time. By setting aside our role as the world's therapist, we may come to accept that we have as much to learn from other cultures' beliefs about the mind as we have to teach.

    Someone [the murderer?] had covered him with a small strip of carpet.Nearby, in a ditch,lay Mrs Chandler - her face and torso bafflingly blanketed in beer cartons.The discovery made international headlines. It swiftly emerged that Dr Bogle, a brilliant specialist in solid state physics, had recently accepted a research post in Washington – and had been preparing to fly there, with his wife and children. Mrs Chandler, who’d worked as a nurse before her marriage, had been at the same New Year’s party with Gilbert Bogle the evening before. They had left separately.Scientists found that the pair had died of acute heart failure – but they could suggest no cause. There were no signs of violence: no smothering or strangulation; no hypodermic marks; no evidence, in the body tissues, of poisons, or radioactive substances of any kind.From the morning the bodies were found, the Bogle-Chandler conundrum would perplex the law’s keenest forensic minds...

    He explains why invisible and unmanaged queues are the underlying root cause of poor product development performance. He shows why these queues form and how they undermine the speed, quality, and efficiency in product development.