Skip to content

Instantly share code, notes, and snippets.

View ryansobol's full-sized avatar

Ryan Sobol ryansobol

  • Ryan Sobol LLC
  • Seattle, WA
  • 23:38 (UTC -07:00)
View GitHub Profile

Deliverables

What I need from you is the following:

  • Access to the source code on GitHub.
  • A production version of your app running somewhere.
  • A completed final questionnaire -- one per team is fine. Here's an example.

These are due Tuesday June 11th by the end of the day.

What's the name of your app?

BlogPress

What does it do?

As the name suggests, BlogPress is a web app for creating and maintaining a blog.

Registered users (aka authors) can create, update, and destroy articles. Authors write articles using Markdown syntax which is converted to HTML on-the-fly.

What's the name of your app?

What does it do?

What's the GitHub url?

@ryansobol
ryansobol / project_questionnaire.md
Last active December 15, 2015 19:59
Project Questionnaire

What's the name (or codename) of your app?

What will your app do?

Who's on your team? What are their roles?

@ryansobol
ryansobol / gist:5276501
Last active December 15, 2015 14:39
What Really Happened at #inspect 2013

What Really Happened at #inspect 2013

For those who couldn't make it to Brussels, here's what you missed.

Dispassionate objectivity

From my experience, great conferences have one thing in common -- debates during, in-between and after talks. #inspect 2013 was no different.

Most speakers had opinions on snake_case vs camelCase. I overheard arguments both for and against Teacup at lunch. Colleagues from around the globe weighed in on the benefits of wrappers and the pitfalls of additional dependencies. Even the venue for #inspect 2014 sparked a catch phrase -- "Tan or tech, Cancun or New York".

@ryansobol
ryansobol / gist:5252653
Last active November 22, 2023 11:53
15 Questions to Ask During a Ruby Interview

Originally published in June 2008

When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.

To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.

What to expect

Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.