Over a million developers have joined DZone.

DevOps Weekly Roundup: Optimizing Code, Bug Testing, and Weird Tricks

DZone's Guide to

DevOps Weekly Roundup: Optimizing Code, Bug Testing, and Weird Tricks

Catch up on the best content from the DevOps zone, hand-picked by our editors.

· DevOps Zone
Free Resource

Download “The DevOps Journey - From Waterfall to Continuous Delivery” to learn learn about the importance of integrating automated testing into the DevOps workflow, brought to you in partnership with Sauce Labs.

Hope everyone had a good weekend! In case you missed them, here's a curated collection of the best and most informative posts from this week's edition of The DevOps Zone. This week: looking at the DevOps hype, using Bazel for CI, the benefits of optimizing code, and bug testing.

Is DevOps the New Black? - Mirco Hering

I spent a lot of time thinking of how to riff on the "Orange is the New Black" theme song, but nothing's coming! Regardless, MVB Mirco Hering reflects on his consulting experience on how everyone is claiming they do DevOps, but simple questions reveal the real truth. Overhyping technology can be a problem in the short term, but it also provokes greater discussion, which is ultimately good. 

One Weird Trick For Fast Continuous Integration - Kristina Chodorow

MVB Kristina Chodorow is focused on Bazel, an open source build tool from Google, and how using it with Jenkins is an improvement over traditional CI pipelines. Her article has a ton of useful diagrams, screenshots, and reports to show you exactly how it works. 

Should We Aspire to Optimize Code Everywhere? - Matt Lacey

Matt Lacey asks the question: "Why are we optimizing in the first place? Because we can, or because it provides a measurable benefit?". In response to a user comment, he explores whether users really care about your optimization efforts, the business perspective, and whether "good enough" really is good enough. 

Record the 'Expected Test Phase' and Improve Your Development Process - Boris Dzhingarov

Lots of teams do not ask for the "expected test phase" for each bug or issue reported, but according to this article, that information can be extremely useful for improving your future processes. Boris goes more in depth about what expected test phases are, and best practices for using that information.

Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure, brought to you in partnership with Sauce Labs

devops ,code quality ,bug testing ,continuous integration ,culture ,jenkins ,build tools

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}