In Case You Missed It: The Most Popular DEV Posts from the Past Week (May 29 - June 4 2017)
Tags: top7
Published: 2017-06-05 14:57:03

---
title: "In Case You Missed It: The Most Popular DEV Posts from the Past Week (May 29 - June 4 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 round up some of the last week's top posts, comments, and tweets. If you have any feedback, please leave a comment._ â¤ï¸

# Feelin' Loopy
<img src = "https://media.giphy.com/media/ugTcpVtsc3gVa/giphy.gif" width = "700">


For-loops are a fundamental concept within programming. Many devs likely remember first encountering them during their first few hours of learning how to code. But are we always using them in the most efficient fashion? Dan Homola summarizes how to execute a tight for-loop in different scenarios:

{% link https://dev.to/danhomola/dont-pay-the-for-looptax %}

Of course, that's not the only way to deal with a loop:

{% tweet 847235394114535424 %}

------

# Save Your Energy
<img src = "https://media.giphy.com/media/3o6Zt6g9GHo3Uxaotq/giphy.gif" width = "700">

Software engineering is just like any other job in that it's easy to burn yourself out. Luckily Moran Danieli-Cohen has a few strategies for staving off that dreadful exhausted feeling. 

{% link https://dev.to/msscohen/3-effective-ways-to-maintain-high-energy-levels-at-work-for-software-engineers %}

Sometimes the solution is as simple as making sure the physical objects you rely on everyday aren't getting too shabby, as was mentioned in the comments:

{% devcomment 8i0 %}

------

# Machine Learning Learning
<img src = "https://media.giphy.com/media/EnGbOzsuBy2Ry/giphy.gif" width = "700">

These days, you're not really a programmer unless you mention machine learning at least a few times per day. But do you actually know the ins and outs of modern predictive modeling? Kasper Fredenslund walks us through some of the basics using the famous iris dataset:

{% link https://dev.to/kasperfred/creating-your-first-machine-learning-classifier-model-in-sklearn %}

------

# Dead on Arrival
<img src = "https://media.giphy.com/media/3o7btYPy2NvzXX0ZmE/giphy.gif" width = "700">

Deadlines are something that almost every company uses in some form to keep employees focused on the task at hand. But if they cause programmers to write bad code just to keep up with the schedule, then they're really doing the whole team a disservice. Jolas Ladis Las discusses:

{% link https://dev.to/jolasladislas/deadlinesbad-reason-for-bad-code %}

If you are going to miss a deadline though, it's best to be honest and communicative:

{% devcomment 940 %}

------
# Words of Wisdom
<img src = "https://media.giphy.com/media/3o7buekRiTqbCEMyis/giphy.gif" width = "700">

There's such emphasis put on embedding computer science into our children's curriculum and making sure the next generation can code that sometimes we might forget that plenty of people have been doing this whole software engineering thing for a while. Ben Hilburn discusses what he sees as the responsibilities of a "senior" engineer:

{% link https://dev.to/bhilburn/on-senior-engineers %}

His list of ten core principles was well-received, but also inspired commenters to add on:

{% devcomment 8nk %}

------
# Mind Your Business
<img src = "https://media.giphy.com/media/xTiTnJxChUjF4u958A/giphy.gif" width = "700">

Most dev.to posts focus on the actual mechanics of writing and deploying good software, but there are of course non-technical aspects to the life of a programmer, especially if you'd like to start a company. Mo Bitar lists some of the key considerations for those looking to start their own business:

{% link https://dev.to/bitario/starting-a-business-as-a-developer-in-2017 %}

------
# Don't Overdo the Docs
<img src = "https://media.giphy.com/media/hYrwRki5WYoZW/giphy.gif" width = "700">

Documentation isn't exactly the most exciting part of a programmer's responsibilities, but it certainly is an important task that routinely gets covered by the dev.to community. Last week Tanja Lichtensteiger spoke about her minimalist approach when it comes to documentation:

{% link https://dev.to/grappleshark/enough-with-documentation %}

Whether you agree with her stance or not, take care in crafting your documentation. Otherwise your users may end up with this feeling:

{% tweet 799721189589520384 %}

_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!_