Over a million developers have joined DZone.

DevOps Zone: Best of the Week (Apr. 19-26)

DZone's Guide to

DevOps Zone: Best of the Week (Apr. 19-26)

· DevOps Zone ·
Free Resource

Discover a centralized approach to monitor your virtual infrastructure, on-premise IT environment, and cloud infrastructure – all on a single platform.

In case you missed them, here is a curated list of the best posts from the past week of The DevOps Zone. This week: You can't have exactly-once-delivery, how to stop worrying and get productive, evolution in software development (an allegory), how acknowledgement is the best motivator, and why software testers should learn to code.

1. You Cannot Have Exactly-Once Delivery

There is no such thing as exactly-once delivery. We must choose between the lesser of two evils, which is at-least-once delivery in most cases. This can be used to simulate exactly-once semantics by ensuring idempotency or otherwise eliminating side effects from operations. Once again, it’s important to understand the trade-offs involved when designing distributed systems. There is asynchrony abound, which means you cannot expect synchronous, guaranteed behavior. Design for failure and resiliency against this asynchronous nature.

2. How to Stop Worrying and Get Productive

There is no shortage of task management software or sites. But one doesn’t need anything fancy. In most cases one doesn’t need more than a simple editable list (a.k.a. a text editor, or a notepad,) and a timer. By planning, knowing where one is going, controlling the effort, and monitoring progress, we are as organized and methodical as we can be, with minimal overhead.

3. Evolution in Software Development

Evolution can be cited as a metaphor for iterative development: every new iteration (or commit at an ideal smallest scale) produces a shippable, new version of the software that has evolved from the previous one. We can take some lessons where patterns observed over million of years of evolution apply to a software development scenario.

4. Acknowledgment as Motivation

Using estimates as motivation *may* be effective in the short term, but in the long term I believe it is dangerous and more likely to negatively affect motivation. As an alternative, in the talk I briefly reviewed Dan Pink's work on motivation that centers on Autonomy, Mastery, and Purpose

5. How Learning to Code Can Make You a Better Software Tester

By arming testers with some coding skills, they will be better able to evaluate the program to ensure it's meeting expectations. They can also work more successfully with developers to execute changes and reduce any issues with the overall product.

Learn how to auto-discover your containers and monitor their performance, capture Docker host and container metrics to allocate host resources, and provision containers.


Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}