Burnout is a very real phenomenon in software development — especially when creating and maintaining open source projects with large numbers of users. Kenneth Reitz shares his personal experiences with developer burnout and his tips for recognizing it, avoiding it, and simply dealing with it.
This is the 2016's anti-brainstorming article by Jake Knapp. Jake tells how he came into realization that structured group brainstorming isn't perfect. He has run hundreds of sprints with startups in fields as diverse as healthcare, farming, and robotics, and came up with an alternative: a five-day process that he calls a design "sprint".
The true purpose of finding the right tools is how it helps the software writer progress in their journey towards mastery. DHH spent his life’s work working with, understanding, and improving Ruby through Rails. In this post, David shares his thoughts on writing good (and bad) software.
Kickstarter recently rewrote the scripts they use to manage their local development environments, with a few goals in mind: making it fast, debuggable and reliable. Aaron Suggs shares how the new scripts helped them slash the amount of time developers spend debugging problems with their local environments.
For the latter half of 2016, Dan Nieves embraced the remote work life — with much of that time as the single remote employee. So as 2016 came to a close, Dan felt like it was a good time to reflect on a few lessons learned from the initial 6 months...
Go or GoLang got very popular in the past couple of years. Go will be the server language of the future - Tobias Lütke, CEO of Shopify. Keval Patel explains the current stage of computer hardware-software and shares his thoughts on why you should learn Go.
Shane Harter, lead engineer at Trulia and Co-Founder of Cronitor.io, summarizes the lessons he learned with Stripe subscriptions, his recommendations, and a few things to watch out.