Diving into the world of software development, DevOps, nutrition, biohacking, and mastering Neovim, sharing tales and tips from the trenches of code and personal wellness.
Feature flags are an instrumental part of continuous deployment. It’s essential to be able to gradually roll out features, but keep them hidden from the production environment until you’re ready to flip the switch. It’s fairly easy to implement this in ES6 with React and Webpack. Here’s an example of how I’ve done it in the past.
Staying on top of your development game means keeping good habits. Here is one tip I always tell people on how to keep your development machine up to date with software so that your next install is speedy.
Remote work is becoming the new norm. We all want to be able to travel and code. So why not always have the best tech setup in your backpack at any given moment? I’ve experimented with lots of gear, and here are my picks for carrying a backpack full of the best gear for coding on the go.
About two years ago, I tried the Soylent diet as a joke. My coworkers had their doubts about it, and to play devils advocate, I decided to give it a try. What started out as an experiment turned out to be a revelation, and I will say that at the time, it changed my life and my approach to food.
My stack of choice for deploying Rails applications is OpsWorks, AWS’s implementation of Chef automated instances. In this article, I’m going to walk you through how my company sets up instances and automates deployments for performance, reliability, and simplicity.
The other day, I was wondering why I can't ignore files in git from the the command line. Unlike some of my co-workers, I don't like using GUI apps for everything, but I still like a little but of automation or simplification on the command line. Do I really need to open .gitignore and add some files or patterns to it? No thanks. Then I googled a bit, and I found git-extras. I found the motherlode of git awesomeness.
I've been in enough hotel rooms (and in the homes of less technically equipped friends) to know what my travel technology kit looks like. When I suspect that I might be in a less-than-ideal environment for connecting and interacting with my devices, I make sure I bring the right gear.
When I first started using Pinboard, I was using it wrong. I integrated it with every IFTTT recipe I could imagine, but I wasn't using it as my main read later service. I used as many recipes chained together as I could to automate tags, but that wasn't even good enough. Delicio.us had an auto tagging function that was less than ideal, and each IFTTT recipe had default tags that cluttered my Pinboard tag cloud. I ended up with a mess of tags that impaired my ability to make sense of my Pinboard queue, and so I barely used it. So, I devised my own multi-step system...
If you've ever worked with ActiveRecord databases, you know how awesome it can be to manage changes to your database. Make some changes in an indexed migration file, and run rake db:migrate to apply all changes; your database stays up to date with each new git pull. Fortunately, there's a way to get the same functionality in regular Ruby code with a Rake task and the Sequel gem.