Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying DevOps Paradox
  • Table Of Contents Toc
  • Feedback & Rating feedback
DevOps Paradox

DevOps Paradox

By : Viktor Farcic
4.3 (7)
close
close
DevOps Paradox

DevOps Paradox

4.3 (7)
By: Viktor Farcic

Overview of this book

DevOps promises to break down silos, uniting organizations to deliver high quality output in a cross-functional way. In reality it often results in confusion and new silos: pockets of DevOps practitioners fight the status quo, senior decision-makers demand DevOps paint jobs without committing to true change. Even a clear definition of what DevOps is remains elusive. In DevOps Paradox, top DevOps consultants, industry leaders, and founders reveal their own approaches to all aspects of DevOps implementation and operation. Surround yourself with expert DevOps advisors. Viktor Farcic draws on experts from across the industry to discuss how to introduce DevOps to chaotic organizations, align incentives between teams, and make use of the latest tools and techniques. With each expert offering their own opinions on what DevOps is and how to make it work, you will be able to form your own informed view of the importance and value of DevOps as we enter a new decade. If you want to see how real DevOps experts address the challenges and resolve the paradoxes, this book is for you.
Table of Contents (21 chapters)
close
close
20
Index
21
Packt

The inevitability of increasing complexity

Viktor Farcic: Does that mean increasing complexity is unavoidable?

Júlia Biró: Exactly, just evolution.

Viktor Farcic: I like that one.

Júlia Biró: Here's the thing. Once you can do something, you put two of those together, and then by the time you have put five together, you feel like, "Oh, this is terrible," and you automate it. Then by the 22nd time you realize that you want that particular instance to be slightly different and that you want to put an if there. You basically want to control it with variables in a full programming language and then, bam! You have created another layer of complexity.

But once you have a programming language with it, there's nothing that's going to stop you from having 5,000, instead of 50. It's easy to say, "Here I have another layer." After that, all you need to do is teach everyone about that and put that into the code, and from there...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
DevOps Paradox
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon