Live data from Hacker News

RailsCasts Retrospective Part 1: The Fuel

rbates.dev

31–40 of 40 posts

Re: RailsCasts Retrospective Part 1: The Fuel

#31
post #23

Thank you all for the kind comments! The Rails community has always been supportive to me. Even criticisms were done in a constructive manner. I will go into detail on why I stopped RailsCasts in part 3, but I will say it wasn’t because of the community. You all have been awesome.

Thank you!

Everything I am and every single penny I've earned can be attributed back to you or M. Hartl. I'm so happy I stumbled into rails 10 years ago.

Re: RailsCasts Retrospective Part 1: The Fuel

#32
This was one of the best resources at the time. I restarted my career as a programmer around that time and looking for realistic samples for known challenges.

Most of the early episodes were precisely those - how to do x?. I ended up purchasing the Pro version for the full team.

Around 2013, I somehow had a feeling it wouldnt last long. High end of the devs cant be living on meager income for a long time, unless they have no family.

Re: RailsCasts Retrospective Part 1: The Fuel

#33
post #23

Thank you all for the kind comments! The Rails community has always been supportive to me. Even criticisms were done in a constructive manner. I will go into detail on why I stopped RailsCasts in part 3, but I will say it wasn’t because of the community. You all have been awesome.

I thought it was because you weren't making enough... How wrong was I lol. I've made a lot of similar videos though and it's an enormous amount of work.

Re: RailsCasts Retrospective Part 1: The Fuel

#36

Earlier quoted context omitted.

A lot of people I've known in this space have run into the problem where making content became their job and it meant they weren't doing the "real work" that created fuel for creating the content. That is, the best content came from talking about the challenges and techniques learnt in their "day job" but now their day job was running a screencast/tutorial business.

I always wonder how the Dilbert author keeps up with office memes given he’s not really in corporate America for quite some time

He is extremely online

Re: RailsCasts Retrospective Part 1: The Fuel

#37
Thanks for RailsCasts Ryan! A few days back I read a thread on how ruby/rails is losing junior devs because of the complexity/can of worms docs of Rails 7. I believe it is because we are missing high quality content like RailsCasts today.

Re: RailsCasts Retrospective Part 1: The Fuel

#38
post #23

Thank you all for the kind comments! The Rails community has always been supportive to me. Even criticisms were done in a constructive manner. I will go into detail on why I stopped RailsCasts in part 3, but I will say it wasn’t because of the community. You all have been awesome.

I just want to say thank you for everything you've done for the rails community. you have been a hero of mine since i started learning rails a decade ago. i hope you are enjoying life and thriving cause you have earned it and deserve it. thank you again for all the help.

Re: RailsCasts Retrospective Part 1: The Fuel

#39
post #28
post #23

Thank you all for the kind comments! The Rails community has always been supportive to me. Even criticisms were done in a constructive manner. I will go into detail on why I stopped RailsCasts in part 3, but I will say it wasn’t because of the community. You all have been awesome.

In the late 2000s and early 2010s, I was working as a C# developer in a big, old, traditional enterprise environment. I had burned out and I was falling out of love with programming. A friend introduced me to Ruby and I became excited again. Railscasts helped me immensely in being able to very quickly build things. This motivated me to continue and before long I was able to change jobs and start using Ruby and Rails…

This pretty much sums up my story exactly as well.

The intangibles on this effort are huge!

Thank you :)

Re: RailsCasts Retrospective Part 1: The Fuel

#40
Ryan Bates Success Formula

1. Apply the "do the simplest thing that could possibly work, get feedback, and iterate on that" principle to any project or idea to gauge interest and get feedback. 2. Reach out to relevant sponsors or partners for support and collaboration. 3. Create content in a consistent and dependable manner to build an audience. 4. Promote content through personal networks and relevant forums or communities. 5. Request feedback from viewers or users to improve and refine content.

Post reply on HN