In Case You Missed It: The Most Popular DEV Posts from the Past Week (May 8 - May 14, 2017)
Tags: top7
Published: 2017-05-15 15:03:45

---
title: "In Case You Missed It: The Most Popular DEV Posts from the Past Week (May 8 - May 14, 2017)"
published: true
description: A round up of the most-read and most-loved contributions from the community this past week.
tags: icymi
cover_image: https://thepracticaldev.s3.amazonaws.com/i/2sfosi733qe5kvlkpch5.png
---

_Every Monday we will round up some of the last week's top posts, comments, and tweets. If you have any feedback, please leave a comment._ â¤ï¸

# Teamwork Makes the Dream Work
<img src = "https://media.giphy.com/media/yEYiScV53Yeo8/giphy.gif" width = "700">

As a veteran employee of Amazon, James Hood has been on some high-pressure, high-impact teams, which required everyone to be on the same page. Toward this end, he reports that "two leadership principles come into play: Think Big and Bias for Action."

{% link https://dev.to/jlhcoder/how-to-set-the-technical-direction-for-your-team %}

------


# Sorting Things Out
<img src = "https://media.giphy.com/media/NLwYHvHIF5pqE/giphy.gif" width = "700">

In her weekly examination of a core computer science principle, Vaidehi Joshi touched upon the value of sorting and how to compare different sorting algorithms:

{% link https://dev.to/vaidehijoshi/sorting-out-the-basics-behind-sorting-algorithms %}

Many programmers never formally took a CS course, so Vaidehi's posts have provided a valuable resource:

{% devcomment 72j %}

------

# A Single-page Specimen
<img src = "https://media.giphy.com/media/rHBPhbA7HnIbe/giphy.gif" width = "700">


In his post "Tour of an Open-Source Elm SPA," Richard Feldman builds a single-page application in Elm and walks us through some of his choices, which he warns is "is not a gentle introduction to Elm": 

{% link https://dev.to/rtfeldman/tour-of-an-open-source-elm-spa %}

------

# Fun While it Lasted
<img src = "https://media.giphy.com/media/3orif8Uufh4J2lRKaQ/giphy.gif" width = "700">

In an emotionally honest piece, Carl Hembrough recalls how he stopped enjoying programming once he started comparing himself to others, leading to an acute case of [imposter syndrome](https://en.wikipedia.org/wiki/Impostor_syndrome).

{% link https://dev.to/carlhembrough/programming-used-to-be-fun %}

It wasn't too surprising that Carl got a lot of positive feedback from dev.to users who resonated with his message:

{% devcomment 7ak %}

------

# Double Trouble
<img src = "https://media.giphy.com/media/LPXRLrwldC6L6/giphy.gif" width = "700">

The difference between different types of test doubles is something many programmers gloss over.

{% tweet 861752022818836481%}

Which is why a summary of their particularities makes for a useful post. Michal Lipski provides one here:

{% link https://dev.to/milipski/test-doubles---fakes-mocks-and-stubs %}

------
# Keeping Things in Order
<img src = "https://media.giphy.com/media/SCYEgsujYeRfq/giphy.gif" width = "700">

Most of us probably use Google's search engine many times per day, often without stopping to question how exactly the results are ordered for us. Indeed Google's PageRank algorithm has long had an air of sorcery and mystique to it–until Sishaar Rao broke it all down for us:

{% link https://dev.to/sishaarrao/demystifying-the-pagerank-algorithm %}

------
# Go with the Flow
<img src = "https://media.giphy.com/media/3oGRFrspEp7mZVQ5vq/giphy.gif" width = "700">

Before beginning a new project, it's important to pick a certain style of git workflow that fits your team's preferences. AbdulBasit Kabir runs through a handful of different styles, from a "Central Workflow" to a "Patch Workflow," and highlights examples for each one

{% link https://dev.to/abulkay/whichs-the-right-git-workflow-for-my-next-project %}

Some commenters reported that they liked to combine aspects of multiple workflows, which AbdulBasit noted was completely valid:

{% devcomment 7co %}

------

_That's it for our weekly wrapup! Keep an eye on Dev.to this week for daily content and discussions...and if you miss anything, we'll be sure to recap it next Monday!_