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.
D'autres épisodes de "Fullstack Ruby Podcast"
Ne ratez aucun épisode de “Fullstack Ruby Podcast” et abonnez-vous gratuitement à ce podcast dans l'application GetPodcast.