29 ratings | 0 reviews | avg rating:4.69

Mirco Hering’s Followers (4)

Mirco’s Bookshelves

to-read (0)
currently-reading (0)
read (29)

Mirco’s Friends

Mirco hasn't connected with their friends on Goodreads, yet.

Mirco Hering

Goodreads Author

Member Since

April 2018

edit data

Combine Editions
Mirco Hering’s books

Average rating: 4.01 · 198 ratings · 16 reviews · 3 distinct works • Similar authors

	DevOps for the Modern Enterprise: Winning Practices to Transform Legacy IT Organizations by Mirco Hering (Goodreads Author), Bhaskar Ghosh (Foreword) 4.01 avg rating — 198 ratings — 4 editions	Error rating book. Refresh and try again. Rate this book Clear rating 1 of 5 stars 2 of 5 stars 3 of 5 stars 4 of 5 stars 5 of 5 stars
	Cooperative Multi-Agent Systems in Automobiles: One Step towards Self Driving Cars 0.00 avg rating — 0 ratings	Error rating book. Refresh and try again. Rate this book Clear rating 1 of 5 stars 2 of 5 stars 3 of 5 stars 4 of 5 stars 5 of 5 stars
	DevOps for the Modern Enterprise: Winning Practices to Transform Legacy IT Organizations 0.00 avg rating — 0 ratings	Error rating book. Refresh and try again. Rate this book Clear rating 1 of 5 stars 2 of 5 stars 3 of 5 stars 4 of 5 stars 5 of 5 stars

* Note: these are all the books on Goodreads for this author. To add more, click here.

Quotes by Mirco Hering (?)

“What Team Structure Is Right for DevOps to Flourish?”
― Mirco Hering, DevOps for the Modern Enterprise: Winning Practices to Transform Legacy IT Organizations

0 likes

“I speak about technical debt quite a bit in this chapter, so I wanted to leave you with a few thoughts on how to measure it. There are, of course, the static code-analysis tools that provide a view of technical debt based on coding issues. I think that is a good starting point. I would add to this the cost to deploy the application (e.g., how many hours of people does it require to deploy into a test or production environment), the cost of regression testing the product (how many hours or people time does it take to validate nothing has broken), and the cost of creating a new environment with the application. If you are more ambitious, you can also look for measures of complexity and dependencies with other applications, but I have not yet seen a good repeatable way for measuring those. The first four I mention are relatively easy to determine and should therefore be the basis for your measure of technical debt.”
― Mirco Hering, DevOps for the Modern Enterprise: Winning Practices to Transform Legacy IT Organizations

0 likes