Reminder from part 1: In this tutorial we’ll build a game that interacts with the Twitter API and challenges users to match a given Tweet with its author. The game is called Following, and you can play the fully-built version of it here: http://followingapp.herokuapp.com.
Keri was born and raised in Parker, Colorado, attended CU-Boulder for her undergraduate degree. During that time, she was a lifeguard, Zamboni driver, and teaching assistant in addition to being a student. She also spent two summers in Costa Rica working with locals and high school students from the US! After graduation she moved to Denver where she worked for a non-profit as a program manager and dental assistant. Wanting to transition back into the technical realm, she moved back to Boulder. Attended gSchool, and has accepted a job here, joining the ever growing QL fam. In her spare time, she loves spending time with family and getting outside to take advantage of all that Boulder has to offer!
Pull request templates for the lazy developer
Denver Business Journal Recognizes the Software Company for Second Consecutive Year
With the announcement of Rails 4.2 came some exciting news: Rails now has built in support for executing jobs in the background with Active Job. The ability to schedule newsletters, follow-up emails, and database housekeeping tasks is vital to almost any production application. In the past, developers had to hand-roll this functionality using gems like Resque Scheduler or Sidekiq Scheduler. With the release of 4.2, setting up jobs for workers to execute at a later time is built in to Rails, making developers' lives easier. In this article, we'll take a look at how to set up Active Job to send a follow up email to a new user in a sample Rails application.
- ← Previous
- Next →