Ruby un Rails (and Proof of Life Update)

Fullstack Ruby Podcast

The rumors are true: I became a Ruby developer because of Rails. It’s probably common that folks find a tech stack or framework which offers the features and the community they desire and so learn the language undergirding that stack. Truth is, Ruby did not appeal to me at first and I resisted it! I wanted to remain a PHP developer, damnit! But the industry draw of Rails required me to learn Ruby, and I eventually fell head-over-heels in love with this language. Now I find myself at a crossroads. Do I leave Ruby behind because I’m no longer a “Rails developer”? Or do I embrace the essence of what makes Ruby Ruby and forge a different path? Gather around, my fellow devs, and listen to my story…
Links & Show Notes

• Ruby, Fully Stacked (Fullstack Ruby rebooted!)
• Using Lambdas and Callables for Deferred Evaluation, Control Flow, and New Language Patterns
• Just a Spec Podcast
• Road to Bridgetown 2.0, Part 1 (Stuck in Burnout Marsh)
• Whitefusion: a Boutique Web Studio (hire me!)

Become a part of the Fullstack Ruby community and learn how to put your Ruby skills to work on the backend AND the frontend. Know somebody who's a JavaScript developer but is interested in learning more about Ruby? Share the site, podcast, or newsletter with them!
Theme music courtesy of Epidemic Sound.

Capitoli

1. Introduction (00:00:00)

2. First becoming a Rubyist in the 2000s (00:02:33)

3. Discovering projects like Opal and Jekyll (00:05:04)

4. Forking Jekyll, launching Bridgetown, and falling in love with Roda (00:07:43)

5. Burnout. (aka What to do about 37signals…) (00:09:32)

6. Ruby has a Rails (and Jekyll) problem (00:11:38)

7. Looking beyond the Rails monoculture (00:13:35)

8. Yes…I still *really* love Ruby! (00:17:33)

9. I also love modern *vanilla* JavaScript… (00:19:45)

10. Full steam ahead in providing Ruby education around Bridgetown & Roda (00:20:45)

11. What do I still get from Ruby I can't get anywhere else? (00:23:31)

12. Outro (00:31:09)