How to Setup Jekyll with Google Plus Comments on Github Pages

21 February 2016

Why migrate to Jekyll?

I’ve had my website set up on Wordpress for the last month. I spent roughly 13 hours setting the site up, with the break down as follows:

  • Install and configure wordpress on Digital Ocean: 30 minutes
  • Research what plugins are needed to nicely manage what’s going on, get markdown for posts: 2 hours
  • Read up on configuring wordpress settings for optimal SEO: 2 hours
  • Finding out that all the plugins I’d researched are currently freemium and you have to install a second set of plugins to add on functionality that used to be free and configuring those plugins to work with the first and not override each others settings: 6 hours
  • Work with different Wordpress themes to find something simple and clean that wouldn’t make your eyes bleed after a long post: 3 hours

After I decided to change themes a few days back, it hit me today that it was all a massive waste of time. It didn’t help that I’m new to wordpress, but taking a couple hours every time I wanted to clean up my site or add a little functionality? Forget about it. Especially when most of what I do is in rails, and when you need to complete some banal task in Rails, you can just search for some gems. Daniel spent some time last week praising Jekyll, so it was fresh on mind and I knew going into it that it take care of many of the problems I had with Wordpress. Namely that my goal in life isn’t to become a Wordpress expert, but to simply code away, and then post my experiences with the minimal amount of added effort.


The 3 Vital Parts Of My Ruby On Rails Development Environment: Tools, Configuration, Location

18 February 2016

Regardless of the language you’re writing, dialing in your environment is what makes or breaks your efficiency. The focus of this post will be on my Ruby environment, namely the configuration and tools I use on a daily basis. This isn’t a comprehensive list, but lists the vitals of my day to day operations. Using and doing the following have saved me countless hours and really given me the room to grow. Use them to break the glass ceiling of inefficiency. After a few months as part of the consulting team at I’ve found a few new tools thanks to the other consultants there, and really solidified my opinion on everything below.


5 Steps to Landing a Ruby on Rails Job: Identify Strengths and Weaknesses (Part 1)

16 January 2016

This is post 2 in a series. For the other parts see:

At this point in the process, you know what you want, and that’s to find a position as a Rails developer. Knowing your goal, how do you get there? There’s really only two options.

  1. Use a system to get what you want.
  2. Blast your resume to everyone and everything that has ‘Rails’ in the job description.

Option 2 is a viable one and can definitely work. However, that depends too much on luck and hoping whatever skills you’re in possession of, a job opening, location and other compatibility to all align. I highly recommend doing this every now and again, but you’d be a hopeful fool to make this your primary strategy. For a sustainable approach to building success and creating maintainable momentum, you need a system. You’re an intelligent person; go for the long game. The start of this process should be reminiscent of a huuuuge freight train getting started. Methodical, powerful, and once it’s up to speed, unstoppable. That’s what you want to become, a mass of forward momentum.


Agile Methodology Outside of Development: 5 Steps to Landing a Ruby on Rails Job (Intro)

12 January 2016

MUST GO FURTHER. If you’ve got a healthy mindset, you’ll know the feeling. Due to a series of (un)fortunate events, August 2015 brought a drive and burning desire into my professional life to a degree I hadn’t known before. My goal: Switch industries and move from a Network Engineer to a Ruby on Rails consultant. There was a lot to learn, and I wanted to break into the consulting world yesterday. The only thing for it was to take the leap and get moving.

This series of posts will detail how I went from cowboy coding to making myself a viable candidate for reputable Rails companies and systematized a way towards success. Content from Patrick McKenzie regarding software development and consulting stoked the fires. Reading Scott Adams of Dilbert fame helped me put down and formalize some loose guidelines I’d assembled for the purpose of maximizing efficiency to land the Rails job I knew I’d get. The following are Agile guidelines tailored for learning new material quickly.

Repeat as needed.


Previous Page: 10 of 10