We learn more from failures than we do from successes. When something goes as expected, we use that process as a mental template for future projects. Success actually stunts the learning process because we think we have established a successful pattern, even after just one instance of success. It is a flawed confirmation that "This is the correct way to do it," which has a tendency to morph into "This is the only way to do it."Real learning comes through crisis.If something goes wrong, horribly wrong, we have to scramble, experiment, hack, scream and taze our way through the process. Our minds flail for new ideas, are more willing to experiment, are more open to external input when we're in crisis mode.The Genesis of an IdeaThat's where the idea for this book came from. When I was in Singapore for DevSecOps Days 2018. Edwin Kwan, Stefan Streichsbier and DJ Schleen were swapping war stories over a couple of beers.The conclusion of their evening of telling tales was the desire to find a way to get those stories out to the community. They spoke with me about putting together a team of authors who would tell their own stories in the hope of helping the DevSecOps Community understand that failure is an option.Yes. You read that right. Failure is an option.Failure is part of the process of making the cultural and technological transformation that needs to happen in order to keep innovating. It is part of the journey to DevSecOps. The stories presented here aren't a roadmap. What they do is acknowledge failure as a part of the knowledge base of the DevSecOps Community.The days of stand-alone security teams isolated from the real process of development are coming to an end. Paraphrasing Caroline Wong, "Security needs to be invited to the party, not perceived as a goon standing at the front door denying admission." With DevSecOps, security is now part of the team.After reading these stories, we hope you will realize you are not alone in your journey. Not only are you not alone, there are early adopters who have gone before you, not exactly "hacking a trail through the swamp,"but at least marking the booby traps, putting flags next to the quick-sandpits and holding up a 'Dragons be here' sign at perilous cave openings

Learn to effectively deliver business aligned cybersecurity outcomes In The CISO Evolution: Business Knowledge for Cybersecurity Executives, information security experts Matthew K. Sharp and Kyriakos “Rock” Lambros deliver an insightful and practical resource to help cybersecurity professionals develop the skills they need to effectively communicate with senior management and boards. They assert business aligned cybersecurity is crucial and demonstrate how business acumen is being put into action to deliver meaningful business outcomes. The authors use illustrative stories to show professionals how to establish an executive presence and avoid the most common pitfalls experienced by technology experts when speaking and presenting to executives. The book will show you how to: Inspire trust in senior business leaders by properly aligning and setting expectations around risk appetite and capital allocation Properly characterize the indispensable role of cybersecurity in your company’s overall strategic plan Acquire the necessary funding and resources for your company’s cybersecurity program and avoid the stress and anxiety that comes with underfunding Perfect for security and risk professionals, IT auditors, and risk managers looking for effective strategies to communicate cybersecurity concepts and ideas to business professionals without a background in technology. The CISO Evolution is also a must-read resource for business executives, managers, and leaders hoping to improve the quality of dialogue with their cybersecurity leaders.

A Washington Post Bestseller Your manual for remote and virtual work. Communicating virtually is cool, useful, and now even more ubiquitous and necessary than ever. But we're often reminded that the quality of human connection we experience in many forms of virtual communication is awful. We've all felt disconnected in a video conference, frustrated that we're not getting through on the phone, upset when our email is badly misinterpreted, or anxious that we're being misunderstood. How can we fix this? In this powerful, practical book, communication expert Nick Morgan outlines five big problems with communication in the virtual world--lack of feedback, lack of empathy, lack of control, lack of emotion, and lack of connection and commitment--and shows how to overcome them as we shift to working remotely more and more. Morgan argues that while virtual communication will never be as rich or intuitive as a face-to-face meeting, recent research suggests that we need to learn is to consciously deliver a whole set of cues, both verbal and nonverbal, that we used to deliver unconsciously in the pre-virtual era. He guides us through this important process, providing rules for virtual feedback, an empathy assessment and virtual temperature check, tips for creating trust in a virtual context, and advice for specific digital channels such as email and text, the conference call, Skype, and more. Whether you're an entrepreneur, an independent professional, or a manager in an organization that has more than one office or customers who aren't nearby, Can You Hear Me? is your essential communications manual for twenty-first-century work.

Through a series of recent breakthroughs, deep learning has boosted the entire field of machine learning. Now, even programmers who know close to nothing about this technology can use simple, efficient tools to implement programs capable of learning from data. This practical book shows you how. By using concrete examples, minimal theory, and two production-ready Python frameworks—Scikit-Learn and TensorFlow—author Aurélien Géron helps you gain an intuitive understanding of the concepts and tools for building intelligent systems. You’ll learn a range of techniques, starting with simple linear regression and progressing to deep neural networks. With exercises in each chapter to help you apply what you’ve learned, all you need is programming experience to get started. Explore the machine learning landscape, particularly neural nets Use Scikit-Learn to track an example machine-learning project end-to-end Explore several training models, including support vector machines, decision trees, random forests, and ensemble methods Use the TensorFlow library to build and train neural nets Dive into neural net architectures, including convolutional nets, recurrent nets, and deep reinforcement learning Learn techniques for training and scaling deep neural nets

This book is an engineering reference manual that explains "How to do DevOps?". It is targeted to people and organizations that are "doing DevOps" but not satisfied with the results that they are getting. There are plenty of books that describe different aspects of DevOps and customer user stories, but up until now there has not been a book that frames DevOps as an engineering problem with a step-by-step engineering solution and a clear list of recommended engineering practices to guide implementors. The step-by-step engineering prescriptions can be followed by leaders and practitioners to understand, assess, define, implement, operationalize, and evolve DevOps for their organization. The book provides a unique collection of engineering practices and solutions for DevOps. By confining the scope of the content of the book to the level of engineering practices, the content is applicable to the widest possible range of implementations. This book was born out of the author's desire to help others do DevOps, combined with a burning personal frustration. The frustration comes from hearing leaders and practitioners say, "We think we are doing DevOps, but we are not getting the business results we had expected." Engineering DevOps describes a strategic approach, applies engineering implementation discipline, and focuses operational expertise to define and accomplish specific goals for each leg of an organization's unique DevOps journey. This book guides the reader through a journey from defining an engineering strategy for DevOps to implementing The Three Ways of DevOps maturity using engineering practices: The First Way (called "Continuous Flow") to The Second Way (called "Continuous Feedback") and finally The Third Way (called "Continuous Improvement"). This book is intended to be a guide that will continue to be relevant over time as your specific DevOps and DevOps more generally evolves.

Managing Humans is a selection of the best essays from Michael Lopp's popular website Rands in Repose(www.randsinrepose.com). Lopp is one of the most sought-after IT managers in Silicon Valley, and draws on his experiences at Apple, Netscape, Symantec, and Borland. This book reveals a variety of different approaches for creating innovative, happy development teams. It covers handling conflict, managing wildly differing personality types, infusing innovation into insane product schedules, and figuring out how to build lasting and useful engineering culture. The essays are biting, hilarious, and always informative.

Effective software teams are essential for any organization to deliver value continuously and sustainably. But how do you build the best team organization for your specific goals, culture, and needs? Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity. In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams. Team Topologies is a major step forward in organizational design for software, presenting a well-defined way for teams to interact and interrelate that helps make the resulting software architecture clearer and more sustainable, turning inter-team problems into valuable signals for the self-steering organization.