Here are 77 books that The Unicorn Project fans have personally recommended if you like
The Unicorn Project.
Shepherd is a community of 12,000+ authors and super readers sharing their favorite books with the world.
I have worked in IT for over 25 years, creating and securing software. I am completely obsessed with ensuring that our software is more reliable, that its integrity can be trusted, and that it keeps our secrets safe. I am not only a computer scientist but an ethical hacker who works hard to create a dialogue between software developers and all of the people who work in our security industry. I am a teacher, a community leader, and a computer nerd who shares messages and lessons wherever she goes.
Accelerate is a book about data. The authors used data collected during their PhD projects in order to prove The DevOps is effective.
They have all sorts of different ways to measure DevOps, it sufficiency, and the fact that way more projects succeed when you do DevOps, rather than waterfall methodology.
The book essentially show can be used as evidence of return on investment when modernizing your IT department. I am a person who loves data, and thus I absolutely love this book. Also, if you listen to the audiobook version, one of the authors reads it to you and her personality really shines through in a fun way.
I really enjoyed listening to Nicole read a book about to me about data!
Accelerate your organization to win in the marketplace.
How can we apply technology to drive business value? For years, we've been told that the performance of software delivery teams doesn't matter that it can't provide a competitive advantage to our companies. Through four years of groundbreaking research to include data collected from the State of DevOps reports conducted with Puppet, Dr. Nicole Forsgren, Jez Humble, and Gene Kim set out to find a way to measure software delivery performance and what drives it using rigorous statistical methods. This book presents both the findings and…
I have worked in IT for over 25 years, creating and securing software. I am completely obsessed with ensuring that our software is more reliable, that its integrity can be trusted, and that it keeps our secrets safe. I am not only a computer scientist but an ethical hacker who works hard to create a dialogue between software developers and all of the people who work in our security industry. I am a teacher, a community leader, and a computer nerd who shares messages and lessons wherever she goes.
The DevOps Handbook is literally an instructional guide on how to do DevOps, properly.
It includes security, it includes how to run operations in a smooth and reliable manner, and of course, how to develop amazing software. It gets into all the nitty gritty, with every detail you would need in order to create a good DevOps system development lifecycle within your organization.
This award-winning and bestselling business handbook for digital transformation is now fully updated and expanded with the latest research and new case studies!
"[The DevOps Handbook] remains a must-read for any organization seeking to scale up its IT capability and expand DevOps practices across multiple departments or lines of business." -Mike Perrow, TechBeacon
For years, The DevOps Handbook has been the definitive guide for taking the successes laid out in the bestselling The Phoenix Project and applying them in any organization. Now, with this fully updated and expanded edition, it's time to take DevOps out of the IT department and…
I have worked in cybersecurity for over 20 years and think it’s one of the most important topics in our modern world. Everyone needs to be secure–from young kids to elderly people avoiding online scams. As a practicing Chief Security Officer, I work with security technology and people every day, and I’m getting to live my childhood dream of being a writer helping people understand these complex challenges. Security is a part of the foundation of Maslow’s Hierarchy of Needs and allows everyone to live up to their full potential as humans. People are the most important part of security, and you don’t need a degree in computer science to be cyber secure.
This book was one of the biggest inspirations for me when I wrote my book.
Running a team of technology experts is really hard, so instead of writing a reference manual or an inspirational leadership memoir, Kim tells the story of a group of people who work together to learn the same best practices that have been in use for decades in the manufacturing and project management industries.
This hits close to home since I can recognize myself and many of my colleagues in each of the vivid characters.
***Over a half-million sold! And available now, the Wall Street Journal Bestselling sequel The Unicorn Project***
"Every person involved in a failed IT project should be forced to read this book."-TIM O'REILLY, Founder & CEO of O'Reilly Media
"The Phoenix Project is a must read for business and IT executives who are struggling with the growing complexity of IT."-JIM WHITEHURST, President and CEO, Red Hat, Inc.
Five years after this sleeper hit took on the world of IT and flipped it on it's head, the 5th Anniversary Edition of The Phoenix Project continues to guide IT in the DevOps revolution.…
I have worked in IT for over 25 years, creating and securing software. I am completely obsessed with ensuring that our software is more reliable, that its integrity can be trusted, and that it keeps our secrets safe. I am not only a computer scientist but an ethical hacker who works hard to create a dialogue between software developers and all of the people who work in our security industry. I am a teacher, a community leader, and a computer nerd who shares messages and lessons wherever she goes.
This book is set in the same universe as The Phoenix Project and The Unicorn Project, but it's at a new company named investments unlimited.
It's also a fictitious story, but with all brand new characters, and brand new problems! In this book they cover security much more deeply than any of the other previous books, talking about how compliance and audit can work together with the information security and DevOps teams.
They talk about common problems that I have faced in many organizations, and a lot of the stories feel so familiar I wonder if the authors have followed me around throughout my career.
Although of course they save the day in the end, there are many parts of the book where we're not quite sure if they're going to make it or not with various characters learning to see things in new ways, so that they can make…
In the vein of the bestselling The Phoenix Project and The Unicorn Project, Investments Unlimited radically rethinks how organizations can handle the audit, compliance, and security of their software systems-even in highly regulated industries. By introducing concepts, tools, and ideas to reimagine governance, Investments Unlimited catalyzes a more humane way to enable high-velocity software delivery that is inherently more secure.
Investments Unlimited, Inc. has accomplished what many other firms in their industry have failed to do: they have successfully navigated the transition from legacy ways of working to the digital frontier. With the help of DevOps practices, Investments Unlimited delivers…
As a professional statistician, I am naturally interested in AI and data science. However, in our current information age, everyone, in all segments of society, needs to understand the basics of AI and data science. These basics include such things as what these disciplines are, what they can contribute to society, and perhaps most importantly, what can go wrong. However, I have found that much of the literature on these topics is highly technical and beyond the reach of most readers. These books are specifically selected because they are readable by virtually everyone, and yet convey the key concepts needed to be data-literate in the 21st century. Enjoy!
This book goes beyond the hype of data science, the details of machine learning methods, and the coding so closely associated with data science. Rather, it emphasizes the real types of problems for which data science may help, and explains the practical issues (“the real work”) that often lead to failure in data science projects.
These issues tend to be overlooked in more technical presentations of data science. They include such critical considerations as defining the right problem to begin with, understanding the “pedigree” (background and quality) of any data used, and ensuring that the right people are involved from the start.
The essential guide for data scientists and for leaders who must get more from their data science teams
The Economist boldly claims that data are now "the world's most valuable resource." But, as Kenett and Redman so richly describe, unlocking that value requires far more than technical excellence. The Real Work of Data Science explores understanding the problems, dealing with quality issues, building trust with decision makers, putting data science teams in the right organizational spots, and helping companies become data-driven. This is the work that spells the difference between a good data scientist and a great one, between a…
My grandfather was a labour activist in Hull in the UK and my father had many classic labour texts such as the book by Tressell, listed below. That got me interested in the world of work and later more specifically in managing people. I moved from studying economics to employment relations /human resource management. Given that most of us (workers) spend 80,000 hours of our lives at work - more time than we are likely to spend on any other activity during our lifetimes - how we spend these lives has remained a source of fascination
Much work on management talks of talent and people being the most important asset, whose ideas and skills should be fully utilized.
This book points to another side of organizations, where stupidity and idiocy reign despite the presence of smart workers (think of people who have important information to convey but are quiet at meetings as they are worried about not being seen as team players). This can help organisations in the short run (less conflict and everyone getting on with the job) but in the long run is problematic.
The authors point to how top-down management marginalizes critical voices and reinforces conformity to existing practices, and in so doing can embed stupidity.
Functional stupidity can be catastrophic. It can cause organisational collapse, financial meltdown and technical disaster. And there are countless, more everyday examples of organisations accepting the dubious, the absurd and the downright idiotic, from unsustainable management fads to the cult of leadership or an over-reliance on brand and image. And yet a dose of stupidity can be useful and produce good, short-term results: it can nurture harmony, encourage people to get on with the job and drive success. This is the stupidity paradox.
The Stupidity Paradox tackles head-on the pros and cons of functional stupidity. You'll discover what makes a…
I taught myself to code back in 1994 while working the graveyard shift as a geologist in the environmental industry. My job consisted of sitting in a chair during the dark hours of the night in a shopping center in Stockton, CA, watching another geologist take samples from wells in the parking lot. A friend of mine suggested I learn to code because I liked computers. I don’t mean to make this out to be a “it’s so simple anyone can do it!” You need to have a relentless drive to learn, which is why I wrote my book, The Imposter’s Handbook - as an active step to learning what I didn’t know I didn’t know.
There’s a section right at the start of this book where the author tries to quantify the value of things he’s learned over the years, and the result is startling.
Think about this for yourself, just in terms of the code you’ve written - how much do you think that’s worth? Your ability to learn things is your key to thriving in this industry, but how well can you recallthose things when you need to?
That’s the point of this whole book: learning to take notes and assemble them into your own personal database. This book led me to Obsidian, which I use relentlessly, and also to Notion, which I also use relentlessly. Writing things down gives me peace of mind and helps me focus and I highly recommend you do the same.
“One of my favorite books of the year. It completely reshaped how I think about information and how and why I take notes.” —Daniel Pink, bestselling author of Drive
A revolutionary approach to enhancing productivity, creating flow, and vastly increasing your ability to capture, remember, and benefit from the unprecedented amount of information all around us.
For the first time in history, we have instantaneous access to the world’s knowledge. There has never been a better time to learn, to contribute, and to improve ourselves. Yet, rather than feeling empowered, we are often left feeling overwhelmed by this constant influx…
Ever since my primary school teacher read out my essay about a friendly octopus to the whole class, I’ve known I was a storyteller. I went on to enjoy a long career as a journalist–first, writing stories about rock and pop groups for the music paper Sounds (where I coined the term ‘The New Romantics’), then as editor of the pop magazine Record Mirror, and subsequently as a writer/editor for national newspapers including The Observer and The Sunday Telegraph. After that, I became a coach, a public speaking trainer, and a book editor. However, my most enduring passion is helping people find and tell their most meaningful stories.
This book should be called "Everything You Ever Wanted to Know About Storytelling but Were Afraid to Ask."
I love the fact that it asks and answers the fundamental question, "So, what is a story?" and explains why humans tell stories, what happens in our brains when we listen to them, and how we instinctively follow story structures.
It gave me a solid introduction to the neuroscience of storytelling and explains why we are predisposed and even designed to think in stories.
Like Stephen Krashen's important work in The Power of Reading, Story Proof collects and analyzes the research that validates the importance of story, story reading, and storytelling to the brain development and education of children and adults. Accomplished researcher and storyteller Kendall Haven, establishes the need for understanding the research findings in neural psychology and brain development and the value of a common definition of story if one is to fully grasp the importance and necessity of story to the development of the human mind. To support his case, he reviews a wealth of research from storytellers, teachers, and others…
I’ve always enjoyed mentoring folks whether new or experienced in programming. Whether it is teaching an intern or a high school robotics student, or onboarding an experienced Java developer, it brings me joy to see people learn. I also love to read. Being able to recommend some of my favorite books can help even more people absorb all of this information.
In addition to Java, you need to know about the Java ecosystem.
Each chapter covers a type of tool like version control, securing binaries, or mobile. Some chapters cover a variety of tools. I particularly liked the overview of Quarkus and Micronaut. I also liked the emphasis of tools vs a role. The analogies were great such as comparing identify/fix/deploy to an oil spill.
The book is 300 pages and easy to carry around. Despite having four authors, the book is very cohesive and reads well.
With the rise of DevOps, low-cost cloud computing, and container technologies, the way Java developers approach development today has changed dramatically. This practical guide helps you take advantage of microservices, serverless, and cloud native technologies using the latest DevOps techniques to simplify your build process and create hyperproductive teams.
Stephen Chin, Melissa McKay, Ixchel Ruiz, and Baruch Sadogursky from JFrog help you evaluate an array of options. The list includes source control with Git, build declaration with Maven and Gradle, CI/CD with CircleCI, package management with Artifactory, containerization with Docker and Kubernetes, and much more. Whether you're building applications with…
I’ve spent more than a decade working on infrastructure, from my early days at LinkedIn, where we had to do a massive DevOps transformation to save the company, to co-founding Gruntwork, where I had the opportunity to work with hundreds of companies on their software delivery practices. From all of this, I can say the following with certainty: the DevOps best practices that a handful of the top tech companies have figured out are not filtering down to the rest of the industry. This is making the entire software industry slower, less effective, and less secure—and I see it as my mission to fix that.
This is one of those books that changed how I thought about and approached software development. First, the book addressed the pain points that I had run into so often: the problems with infrequent, manual deployments, the outages caused by changing configuration rather than source code, the nightmare of merge conflicts that you get from long-lived feature branches, and so on.
Then, it showed how to flip the typical software development process on its head through CI / CD, changing the default from “our software is broken, and we need an integration and release process to get it working” to “our software is always working, and we can release it at any time.” Once I read it, I could never go back to the old way.
Getting software released to users is often a painful, risky, and time-consuming process.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,…
