McCord helped create the unique and high-performing culture at Netflix, where she was chief talent officer. In her new book, Powerful: Building a Culture of Freedom and Responsibility, she shares what she learned there and elsewhere in Silicon Valley.McCord advocates practicing radical honesty in the workplace, saying good-bye to employees who don’t fit the company’s emerging needs, and motivating with challenging work, not promises, perks, and bonus plans. McCord argues that the old standbys of corporate HR―annual performance reviews, retention plans, employee empowerment and engagement programs―often end up being a colossal waste of time and resources. Her road-tested advice, offered with humor and irreverence, provides readers a different path for creating a culture of high performance and profitability.Powerful will change how you think about work and the way a business should be run.

    Yet until now, few have recognized how relevant these powerful ideas are to individuals and their daily work. Every person at a desk, drafting table, workstation, or operating table must (like a factory) deal with the challenge of reducing the waste that creeps into their work. The same Lean principles that have improved efficiencies on the factory floor can be just as powerful--in fact, far more so--in helping individuals boost personal performance.Winner of a 2013 Shingo Research and Professional Publication Award!A Factory of One: Applying Lean Principles to Banish Waste and Improve Your Personal Performance describes how you can foster a new mindset and improve your performance by applying Lean methods to your work. It translates powerful Lean tools such as visual management, flow, pull, 5S, and kaizen to your daily work, revealing how they can help to improve efficiency, reduce waste, and link you ever more closely to customer value. This practice will help you develop better self-awareness, more disciplined problem-solving skills, and the ability to self-correct errors.This book not only provides the tools, but also teaches you how to find the root causes underlying your inefficiencies so you can eliminate them permanently. It will enable you to immediately improve personal productivity while developing the skills needed for continuous improvement. It includes real-world examples that illustrate how these principles have been successfully applied across a range of industries. Providing the perfect mix of what-to-do with why-to-do it, the text details a step-by-step approach to applying Lean principles to your work.Listen to what Daniel Markovitz has to say about his new book, A Factory of One.Part One -- Part Two View the book's website at www.afactoryofone.com.View the author's website at www.timebackmanagement.com.

    Some books try to give you copy-and-paste instructions for how to deal with every single system issue that may arise, but How Linux Works actually shows you how the Linux system functions so that you can come up with your own solutions. After a guided tour of filesystems, the boot sequence, system management basics, and networking, author Brian Ward delves into open-ended topics such as development tools, custom kernels, and buying hardware, all from an administrator's point of view. With a mixture of background theory and real-world examples, this book shows both "how" to administer Linux, and "why" each particular technique works, so that you will know how to make Linux work for you.

    You've just been introduced to your new team as their Agile Coach. The team calls themselves The Dream Team. You are responsible for coming up with a plan to get the team back on track to achieve their project goals.Shortly after the initial product launch, The Dream Team was set a challenge by the Management Team to try out an alternative way of working called Agile. Eighteen months on and the team is working anything but like a dream. In fact, life's become a bit of a nightmare. Morale is low. Productivity has ground to a halt. Quality has become a taboo subject.Management believes the project has reached an impasse. They demand results and are prepared to outsource the remainder of the project. You have 5 days to figure out how to help the team move forward.Your fate and that of your team is entirely in your hands. What choices will you make? Choose badly and you’ll come to a sticky end. Choose wisely and you and your team stand a chance of living happily ever after. What will you choose to do?

    Visible Ops is comprised of four prescriptive and self-fueling steps that take an organization from any starting point to a continually improving process. MAKING ITIL ACTIONABLE Although the Information Technology Infrastructure Library (ITIL) provides a wealth of best practices, it lacks prescriptive guidance: What do you implement first, and how do you do it? Moreover, the ITIL books remain relatively expensive to distribute. Other information, publicly available from a variety of sources, is too general and vague to effectively aid organizations that need to start or enhance process improvement efforts. The Visible Ops booklet provides a prescriptive roadmap for organizations beginning or continuing their IT process improvement journey. WHY DO WE NEED VISIBLE OPS? The Visible Ops methodology was developed because there was not a satisfactory answer to the question: "I believe in the need for IT process improvement, but where do I start?" Since 2000, Gene Kim and Kevin Behr have met with hundreds of IT organizations and identified eight high-performing IT organizations with the highest service levels, best security, and best efficiencies. For years, they studied these high-performing organizations to figure out the secrets to their success. Visible Ops codifies how these organizations achieved their transformation from good to great, showing how interested organizations can replicate the key processes of these high-performing organizations in just four steps: 1. Stabilize Patient, Modify First Response - Almost 80% of outages are self-inflicted. The first step is to control risky changes and reduce MTTR by addressing how changes are managed and how problems are resolved. 2. Catch and Release, Find Fragile Artifacts - Often, infrastructure exists that cannot be repeatedly replicated. In this step, we inventory assets, configurations and services, to identify those with the lowest change success rates, highest MTTR and highest business downtime costs. 3. Establish Repeatable Build Library - The highest return on investment is implementing effective release management processes. This step creates repeatable builds for the most critical assets and services, to make it "cheaper to rebuild than to repair." 4. Enable Continuous Improvement - The previous steps have progressively built a closed-loop between the Release, Control and Resolution processes. This step implements metrics to allow continuous improvement of all of these process areas, to best ensure that business objectives are met.

    With the 97 short and extremely useful tips for programmers in this book, you'll expand your skills by adopting new approaches to old problems, learning appropriate best practices, and honing your craft through sound advice.With contributions from some of the most experienced and respected practitioners in the industry--including Michael Feathers, Pete Goodliffe, Diomidis Spinellis, Cay Horstmann, Verity Stob, and many more--this book contains practical knowledge and principles that you can apply to all kinds of projects.A few of the 97 things you should know:"Code in the Language of the Domain" by Dan North"Write Tests for People" by Gerard Meszaros"Convenience Is Not an -ility" by Gregor Hohpe"Know Your IDE" by Heinz Kabutz"A Message to the Future" by Linda Rising"The Boy Scout Rule" by Robert C. Martin (Uncle Bob)"Beware the Share" by Udi Dahan

     At any given moment, somewhere in the world someone struggles with the same software design problems you have. You know you don't want to reinvent the wheel (or worse, a flat tire), so you look to Design Patterns--the lessons learned by those who've faced the same problems. With Design Patterns, you get to take advantage of the best practices and experience of others, so that you can spend your time on...something else. Something more challenging. Something more complex. Something more fun. You want to learn about the patterns that matter--why to use them, when to use them, how to use them (and when NOT to use them). But you don't just want to see how patterns look in a book, you want to know how they look "in the wild". In their native environment. In other words, in real world applications. You also want to learn how patterns are used in the Java API, and how to exploit Java's built-in pattern support in your own code. You want to learn the real OO design principles and why everything your boss told you about inheritance might be wrong (and what to do instead). You want to learn how those principles will help the next time you're up a creek without a design pattern. Most importantly, you want to learn the "secret language" of Design Patterns so that you can hold your own with your co-worker (and impress cocktail party guests) when he casually mentions his stunningly clever use of Command, Facade, Proxy, and Factory in between sips of a martini. You'll easily counter with your deep understanding of why Singleton isn't as simple as it sounds, how the Factory is so often misunderstood, or on the real relationship between Decorator, Facade and Adapter. With Head First Design Patterns, you'll avoid the embarrassment of thinking Decorator is something from the "Trading Spaces" show. Best of all, in a way that won't put you to sleep! We think your time is too important (and too short) to spend it struggling with academic texts. If you've read a Head First book, you know what to expect--a visually rich format designed for the way your brain works. Using the latest research in neurobiology, cognitive science, and learning theory, Head First Design Patterns will load patterns into your brain in a way that sticks. In a way that lets you put them to work immediately. In a way that makes you better at solving software design problems, and better at speaking the language of patterns with others on your team.

    The modern economy—the world itself—relies on technology. Demand for the people who can produce it far outweighs the supply. So why do developers occupy largely subordinate roles in the corporate structure? Developer Hegemony explores the past, present, and future of the corporation and what it means for developers. While it outlines problems with the modern corporate structure, it’s ultimately a play-by-play of how to leave the corporate carnival and control your own destiny. And it’s an emboldening, specific vision of what software development looks like in the world of developer hegemony—one where developers band together into partner firms of “efficiencers,” finally able to command the pay, respect, and freedom that’s earned by solving problems no one else can. Developers, if you grow tired of being treated like geeks who can only be trusted to take orders and churn out code, consider this your call to arms. Bring about the autonomous future that’s rightfully yours. It’s time for developer hegemony.

    Yet, managing human beings and navigating complex product roadmaps is no easy task, and it's rare to find a product leader who can steward a digital product from concept to launch without a couple of major hiccups. Why do some product leaders succeed while others don't?This insightful book presents interviews with nearly 100 leading product managers from all over the world. Authors Richard Banfield, Martin Eriksson, and Nate Walkingshaw draw on decades of experience in product design and development to capture the approaches, styles, insights, and techniques of successful product managers. If you want to understand what drives good product leaders, this book is an irreplaceable resource.In three parts, Product Leadership helps you explore:Themes and patterns of successful teams and their leaders, and ways to attain those characteristicsThe best approaches for guiding your product team through the startup, emerging, and enterprise stages of a company's evolutionStrategies and tactics for working with customers, agencies, partners, and external stakeholders

    With this hands-on guide, you'll learn how to write effective, idiomatic Python code by leveraging its best and possibly most neglected features. Author Luciano Ramalho takes you through Python's core language features and libraries, and shows you how to make your code shorter, faster, and more readable at the same time.Many experienced programmers try to bend Python to fit patterns they learned from other languages, and never discover Python features outside of their experience. With this book, those Python programmers will thoroughly learn how to become proficient in Python 3.This book covers:Python data model: understand how special methods are the key to the consistent behavior of objectsData structures: take full advantage of built-in types, and understand the text vs bytes duality in the Unicode ageFunctions as objects: view Python functions as first-class objects, and understand how this affects popular design patternsObject-oriented idioms: build classes by learning about references, mutability, interfaces, operator overloading, and multiple inheritanceControl flow: leverage context managers, generators, coroutines, and concurrency with the concurrent.futures and asyncio packagesMetaprogramming: understand how properties, attribute descriptors, class decorators, and metaclasses work"

    If we can understand what makes these gatherings effective and memorable, then we can reframe and redirect them to benefit everyone, host and guest alike. Parker defines a gathering as three or more people who come together for a specific purpose. When we understand why we gather, she says -- to acknowledge, to learn, to challenge, to change -- we learn how to organize gatherings that are relevant and memorable: from an effective business meeting to a thought-provoking conference; from a joyful wedding to a unifying family dinner. Drawing on her experience as a strategic facilitator who's worked with such organizations as the World Economic Forum, the Museum of Modern Art, and the retail company Fresh, Parker explains how ordinary people can create remarkable occasions, large and small. In dozens of fascinating examples, she breaks down the alchemy of these experiences to show what goes into the good ones and demonstrates how we can learn to incorporate those elements into all of our gatherings. The result is a book that's both journey and guide, full of big ideas with real-world applications that will change the way you look at a business meeting, a parent-teacher conference, and a backyard barbecue.

    Features chapters on finance, marketing, accounting, strategy, quantitative analysis, operations, economics, organisational behaviour, and ethics, all revised to reflect the contemporary corporate culture and economic climate.

    The first type drain intelligence, energy, and capability from the ones around them and always need to be the smartest ones in the room. These are the idea killers, the energy sappers, the diminishers of talent and commitment. On the other side of the spectrum are leaders who use their intelligence to amplify the smarts and capabilities of the people around them. When these leaders walk into a room, lightbulbs go off over people's heads, ideas flow, and problems get solved. These are the leaders who inspire employees to stretch themselves to deliver results that surpass expectations. These are the Multipliers. And the world needs more of them, especially now, when leaders are expected to do more with less. In this engaging and highly practical book, leadership expert Liz Wiseman and management consultant Greg McKeown explore these two leadership styles, persuasively showing how Multipliers can have a resoundingly positive and profitable effect on organizations—getting more done with fewer resources, developing and attracting talent, and cultivating new ideas and energy to drive organizational change and innovation. In analyzing data from more than 150 leaders, Wiseman and McKeown have identified five disciplines that distinguish Multipliers from Diminishers. These five disciplines are not based on innate talent; indeed, they are skills and practices that everyone can learn to use, even lifelong and recalcitrant Diminishers. Lively, real-world case studies and practical tips and techniques bring to life each of these principles, showing you how to become a Multiplier too, whether you are a new or an experienced manager. Just imagine what you could accomplish if you could harness all the energy and intelligence around you. Multipliers will show you how.

    On the one hand, there are the more agile methods that focus on individual projects, and how to get them done fast--the camp represented by Beck and Cockburn. On the other hand, there are the more disciplined methods, focused on setting up organizational processes for getting projects done with predictable high quality--the camp best represented by the SEI, the CMMI, and Humphrey. Although these methods are often presented as mutually exclusive, they actually lie on a continuum. The authors of Balancing Agility and Discipline have worked out clear guidelines for determining where on that continuum a particular software development project is located--and therefore, how agile or disciplined a chosen methodology can or has to be.

    His second book is the natural extension of Start with Why, expanding his ideas at the organizational level. Determining a company’s WHY is crucial, but only the beginning. The next step is how do you get people on board with your WHY? How do you inspire deep trust and commitment to the company and one another? He cites the Marine Corps for having found a way to build a culture in which men and women are willing to risk their lives, because they know others would do the same for them. It’s not brainwashing; it’s actually based on the biology of how and when people are naturally at their best. If businesses could adopt this supportive mentality, employees would be more motivated to take bigger risks, because they’d know their colleagues and company would back them up, no matter what. Drawing on powerful and inspiring stories, Sinek shows how to sustain an organization’s WHY while continually adding people to the mix.