What's ExploreRails all about?

ExploreRails will be a series of screencasts (eventually lots of screencasts) that dig deep into the depths of the Rails source code. We'll look into how Rails implements many of its "magical" features in hopes that the understanding gained helps us write better Rails apps.

Why ExploreRails?

I think exploring the Rails source is an important part of becoming a more seasoned, mature, efficient, and knowledgable Rails developer. That said, diving into a code base that large and complex is not always easy or straightforward. I hope these screencasts bridge that gap, helping you get from "How'd it do that?" to "I see what they did there!"

Who is ExploreRails for?

This series will be targeted at Intermediate to Advanced Rails users who wish to gain a deeper understanding of how Rails works and use that knowledge to build better, stronger Rails apps. It would also serve as a resource for Rubyists of all levels, giving an insight into how one of the most popular Ruby implementations is built.

What's the plan?

The plan is to create an inaugural series of 6 episodes. I'll probably use the Rails guides as inspiration of areas to dive into. (I'm also open to suggestions.) I expect try to keep each episode at 30 minutes, though that may change depending on the content.

When will the series be available to the public?

I'll start to release the video series to general public one month after it's been made available to the backers. I will make the inaugural 6 episodes available free of charge at that point. (I still haven't decided whether to roll them out all at once or one at a time...we'll see.)

What about future videos?

I would love to continue on past the inaugural 6 episodes. I definitely think there is enough Rails to explore. I think after the first 6 I'll have a much better idea of what works and what doesn't work as far as content, format, costs, and funding required.

What do I know about Rails?

I've been using Rails daily for the last 6 years. (It'll be 7 in August.) You don't use Rails that long without spending a fair amount of wading through the source. I've devoted a good chunk of 2012 to spending more focused time digging into, understanding, and contributing to Rails. I have a few accepted Pull Requests to show for it and am currently leading a mini-series dive into Active Support at the monthly Dallas Ruby meetings. I also work full time with one of the largest and most talented groups of Ruby and Rails developers on the planet at LivingSocial.

Why use Kickstarter for these screencasts?

Good question. The first answer is to gauge interest. I think this could be really cool. I've talked to a few people who think the same. But screencasts are a lot of effort. I want to make sure I'm spending my time on stuff people want and this avenue helps me figure out if this is one of those things.

The second answer is that there is some cost with gearing up to create high quality screencasts. I would also like to get some help for things like logo, animations, and other things to help take the polish up a notch.  The remainder will cover the time that will go into researching, recording, and producing each video.

Why do I want to do this?

I love to solve problems and I use software when necessary. When I need to build software to solve problems, I love doing that with Ruby. When I need to build software for the web, I love doing that with Rails. The more I read the Rails source code, the more I understand Rails and Ruby. The more I understand Ruby and Rails, the more I enjoy using them to solve problems.

I want to help others feel that. I think this is one way I can try and do that.

---

Why would you post a blurry screencast when trying to get funding for a series of screencasts?

The original is much better...I'm sure the Kickstarter encoding took a bit out of it. Figuring out how to best deliver high quality video will be part of the adventure! :)