66 books like The Unicorn Project

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!

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 is a technical book with technical examples.

The Phoenix Project is a storybook about affect fictious company called parts unlimited.

I swear I must have worked at this company at some point in my career, it feels so familiar! It follows a story of an organization that used waterfall in order to make software and all the problems that happened from using this very old software development methodology.

Throughout the story they ‘discover’ how to do DevOps, slowly improving all of their process is until they have a smooth-oiled software creation machine. This includes many stories about security and why the old ways of doing information security just don't work within a DevOps environment.

The characters in this book are both lovable, and relatable. I would never have thought a fictitious story about an IT department could be so fun to read!

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… show more.

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.

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.

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 recall those 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.

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.

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.

The importance of Extreme Programming can’t be overstated.

Kent Beck created one of the few Agile methods that captured not just a process for managing work, but a set of practices that would keep your software manageable in the long run. Shortly after this book was published, the Agile Manifesto was created.

You might say, “the rest is history”, except the industry lost its way for a decade. Extreme Programming was revived in Dave Farley and Jez Humble’s Continuous Delivery – now a vital part of DevOps. The State of DevOps report has validated at least half of the Extreme Programming practices, and Continuous Delivery brings it to the fore once more.