Plus... Introduction to Code Churn | 20 Patterns to Watch for in Your Engineering Team
View as Web Page | Unsubscribe
 
 
 
 
 
 
 
 
Hi, recommended for you...
 
 
 
The 5 Foundational DevOps Practices: How to Establish and Build on Them
 
Introduction to Code Churn
 
The Myth: Docker vs Kubernetes vs Mesos
 
20 Patterns to Watch for in Your Engineering Team
 
 
 
 
EndPoint-Buyers
The 5 Foundational DevOps Practices: How to Establish and Build on Them
 

As your org progresses through its DevOps journey, what are the best practices that submitful teams use that you should follow? Puppet and Splunk surveyed more than 3,000 participants and the findings reveal a set of core DevOps practices that are critical for submit. Discover what separates submitful DevOps teams from those that fail, and learn the next steps to take on your DevOps journey.

Download this guide to learn:

  • Key practices required to be a mature DevOps organization
  • Why collaboration is paramount to a team’s submit
  • The importance of real-time monitoring and observability, and key metrics to track
 
 
 
 
Pluralsight_Churn

 

Introduction to Code Churn
 
Among the metrics that managers can use to understand a team’s progress is Code Churn. Code Churn is when a developer re-writes their own code shortly after it has been checked in (typically within three weeks). It’s typically a natural part of an engineer’s workflow as they explore, test, and refine their work — but unusually high levels of churn or unexpected fluctuations in the metric can be used as a signal that something’s off.

Watching trends in code churn can help managers notice when a deadline is at risk, when an engineer is stuck or struggling, or when there are issues concerning external stakeholders.

In this guide, we’ll unpack what code churn is, what it isn’t, and what to do when you notice an unexpected spike in the metric.
 
 
 
 
Myth
The Myth: Docker vs Kubernetes vs Mesos
 

These days it seems like container orchestration is a big topic in every technical conversation. There are countless articles, presentations, and lots of social chatter comparing Docker, Kubernetes, and Mesos. However, many of these articles and talk-tracks are misinformed and perpetuate the myth that these three open source projects are in a fight-to-the-death for container supremacy.

While all of these platforms have functionality around containers, they are all very different technologies that do very different things. In this infographic, we aim to dispel these myths and provide clarity around what these technologies do and how they are different. Read on to learn more about Kubernetes, Docker, Apache Mesos, and how they all actually work together.

 
 
 
 
Engineering

 

20 Patterns to Watch for in Your Engineering Team
 
Effective managers view their teams as complex interdependent systems, with inputs and outputs. When the outputs aren't as expected, great managers approach the problem with curiosity and are relentless in their pursuit of the root cause. They watch code reviews and visualize work patterns, spotting bottlenecks or process issues that, when cleared, increase the overall health and capacity of the team.

20 Patterns is a collection of work patterns we've observed in working with hundreds of software teams. Our hope is that you'll use this field guide to get a better feel for how the team works, and to recognize achievement, spot bottlenecks, and debug your development process with data.
 
 
 
 
 
ebulletins
 
 
444 N. Michigan Avenue, Chicago, IL 60611 USA

You received this email because you are subscribed to 'CodeCraft Weekly' from ebulletins. If you have any questions regarding your subscription, articles or links in this email, please contact us.

To unsubscribe click below
Unsubscribe via email Unsubscribe@Techebulletins.com
Unsubscribe via phone (888) 781 0133

ebulletins are published by DemandWorks Media LLC.
 
 
 
Update Your Email Preferences | Unsubscribe | Privacy Policy | Support
 
 
- - - - - - - - - - - - - - - - - - - - - - -