Updated RailsCasts Status
railscasts.com
Updated RailsCasts Status
1–10 of 26 posts
Re: Updated RailsCasts Status
#2I'm happy about how open Ryan has been about this whole thing. We all suffer from burnout from time to time.
Re: Updated RailsCasts Status
#3I'm sad to see this happen as Ryan not only produces great screencasts but shows the trends and popular gems along the way. I respect his decision, though - I know what burnout feels like and it's the biggest mental burden one can have. Good luck, Ryan!
Re: Updated RailsCasts Status
#4This is the best way to handle it, just a quick note saying "Sorry, maybe soon!" rather than out and out abandoning ship. Kudos to him, I hope he finds his desire for it again, he makes some excellent resources.
Re: Updated RailsCasts Status
#5Nicely handled. Good for you, take your time Ryan. You've given so much quality free content over the years, the least the Rails community can do is hang back and let you figure this out on your own good time.
Re: Updated RailsCasts Status
#6Recovering from a burn out myself too.
Took it easy for a couple of months, went on some holidays, and now helping a startup out at the lisbon challenge.
Good luck ryan!
Re: Updated RailsCasts Status
#7I think this speaks of a larger trend with the Rails platform. What I mean is that it's now a mature platform and Railscasts have covered a lot of ground. My guess is part of the burnout Ryan is experiencing is due to a dwindling amount of material to cover without venturing outside of the platform, which he has been doing (and is welcome).
While I love Rails and Ruby (and learned a ton from Railscasts), the future of the web is building a separate RESTful API + separate static JavaScript browser app + any other devices like mobile, Glass, etc (opposed to nesting client-side JS apps under assets).
Edit: In response to the downvotes, let me clarify: I think Ryan is running out of topics in the context of Rails. He's a great teacher and I'm a paid pro subscriber.
Re: Updated RailsCasts Status
#8I think this speaks of a larger trend with the Rails platform. What I mean is that it's now a mature platform and Railscasts have covered a lot of ground. My guess is part of the burnout Ryan is experiencing is due to a dwindling amount of material to cover without venturing outside of the platform, which he has been doing (and is welcome). While I love Rails and Ruby (and learned a ton from Railscasts), the future o…
How did you infer that from "I don't want to return until I am fully ready to avoid getting burnt out."?
Re: Updated RailsCasts Status
#9Take your time Ryan! Not sure what exactly that you are going/went through. But your style and topics you covered were/are still unparalleled and sorely missed in the Rails world.
Ryan, if you are reading these: You have been doing Rails stuff for quite a while now. If you think, its getting repetitive and not challenging enough, it might not be a bad idea to diversify the screen casts away from Rails. Node, golang or anything that ignites the keen learner in you. I am sure you will do a great job making those technologies accessible to the uninitiated. Of course Ryan knows best :)
Re: Updated RailsCasts Status
#10I feel like I owe such a huge debt to Ryan and don't even want him to feel the pressure of 'coming back'... as he already gave so much. Burnout is a serious issue for those that make a living behind a keyboard.
That being said - how would you reenergize in his shoes?
He's been chasing the edge of Rails development for so long - is that where the subscribers come from?
It seems like he gets OVER THE TOP response every time he does a more 'newbie' Railscast - so maybe here are some options to maybe reenergize and keep the subscriber base - what would you like to see?
- More Rails newbie stuff - Exactly like before, after a break - More Multi-session 'building a complete app' - Guest speaker sessions - Evolve to more of a 'how to tackle programmer challenges' - Evolve to more of a 'building web apps' vs. 'only Rails' (ember, meteor, Go)
What else?