With the basics, the key is to stay simple and cheap. As with all hobbies, it makes little sense to invest heavily in equipment until you’re consistent, and know you’re sticking with it for the long haul. Once you near intermediate level, you likely will not achieve significant leaps in progress through improving your form, so now is the time to buy your way to new PRs.
When I first started lifting, I’d see giant dudes at the gym lugging comically large duffel bags, filled with who-knows-what, and would wonder how anyone thought all of that stuff was necessary. Fast-forward seven years, and now I’m somehow one of those dudes.
Life at the gym used to be quite simple. But as the years went on, and I worked with increasingly heavy weights, I slowly added tools to help me in my quest for strength.
This is the first in a series of posts to document my accumulation of lifting gear, starting with the bare bones essentials…
Updated November 12, 2016 with available videos from touchlab
This year I was lucky enough to attend DroidCon NYC, and soak up as much Android dev goodness as I could. There were a bunch of interesting talks, for a varying degree of knowledge level. Definitely something for everyone, something I can speak to, being I am very new to mobile/Android development.
During the conference, I seemed to find myself in the most popular talks, so when I could get a seat, I tried to take notes. I’ll compile them here so they can benefit more than just me.
A few years back, there was a big push for HTTPS Everywhere, big enough for Google to modify their page ranking for it.
over the past few months we’ve been running tests taking into account whether sites use secure, encrypted connections as a signal in our search ranking algorithms. We’ve seen positive results, so we’re starting to use HTTPS as a ranking signal.
Considering that a big reason for me to have this blog is so I can own my search results, I decided to take some time to get that sweet green lock everyone seemed to like so much…
The break was caused by a seemingly common issue for Emacs users in OS X: the PATH variable as Emacs understood it was not the PATH that terminal used. Now that my Git config was telling Git to call out to the GNUPG binary to sign the commit, and it couldn’t find it.
When you are working in a Ruby shop that doesn’t completely subscribe to the Majestic Monolith™ mindset, you’ll probably end up with some domain logic that needs to be shared across your apps/services. In Ruby Land, that means encapsulating that logic into a gem, so all of your applications can have consistent logic.
Git itself has supported signing your work for a while, but I think this new visibility into being a good “Git Citizen” will encourage more people to start using that feature.
Cloud Native Staff Engineer @ Blue Apron, powerlifter, big eater, steak aficionado 🥩