I've landed a gig with option 2, and Rails/Ruby wasn't even a language/framework that I've used before. I'm primarily a JS/React developer, but those skills were enough to land me a spot at a local company, and I'm learning ruby/rails on the job. I also do not have a degree, or any college experience. Its definitely got its transferable skills if you have some sort of understanding of programming as well. I'm picking it up fairly quickly, and in the case of the actual work? I'm working on projects that are already set up, and existing, doing feature additions, and bug fixes, so the majority of the heavy lifting is done. I can focus more on logic and flow of the framework as opposed to learning everything all at once and its definitely super nice! Being able to focus on building out additional methods in helpers, or making a new view, or even just tweaking them is a way nicer foot in the door to learning the framework than starting everything on my own.
I wish I had found this video sooner! I wish I heard of the top-down approach. I started from the bottom to up and it was painful! I am now 1 year and 2 months into full stack development and I wish I jumped into a framework much sooner like you recommended. I feel as if I had started top down, I would be leagues ahead compared to where I am at this present moment.
I am really confiddent enough in my Rails skill but I could not able to get freelancing jobs. With 4+ experience in Ruby and 3+ years experience in Rails. I am depressed recently.
Your bicycle riding metaphor is more applicable to someone using a web app, not building it. The developer is the one building "the bicycle" not the one "riding it".
@@mixandgo well, in that case you don't need to know how Rails is built. But I can't imagine someone's gonna have a fun time trying to build Rails apps without knowing what a class method is. And it's a PITA to read documentation without understanding what "accepts a block and yields x to it" means.
@@em_the_bee you are perfectly right. But guess what. The curiosity/frustration keeps you motivated to learn. It's a way of discovering through practice.
I've landed a gig with option 2, and Rails/Ruby wasn't even a language/framework that I've used before. I'm primarily a JS/React developer, but those skills were enough to land me a spot at a local company, and I'm learning ruby/rails on the job. I also do not have a degree, or any college experience.
Its definitely got its transferable skills if you have some sort of understanding of programming as well. I'm picking it up fairly quickly, and in the case of the actual work? I'm working on projects that are already set up, and existing, doing feature additions, and bug fixes, so the majority of the heavy lifting is done. I can focus more on logic and flow of the framework as opposed to learning everything all at once and its definitely super nice! Being able to focus on building out additional methods in helpers, or making a new view, or even just tweaking them is a way nicer foot in the door to learning the framework than starting everything on my own.
Congrats. And thanks for sharing.
Thank you so much for actual directed advice! It has a flow and a goal! I will keep you updated with my progress!
Any update?
I wish I had found this video sooner! I wish I heard of the top-down approach. I started from the bottom to up and it was painful! I am now 1 year and 2 months into full stack development and I wish I jumped into a framework much sooner like you recommended. I feel as if I had started top down, I would be leagues ahead compared to where I am at this present moment.
That's true, but it's never too late. You can always pick a higher abstraction (i.e., project management, building a business) and learn much faster.
I am really confiddent enough in my Rails skill but I could not able to get freelancing jobs. With 4+ experience in Ruby and 3+ years experience in Rails. I am depressed recently.
Getting freelancing gigs is much more about sales and marketing than tech skills.
Maybe your offer isn't right?
Your bicycle riding metaphor is more applicable to someone using a web app, not building it. The developer is the one building "the bicycle" not the one "riding it".
Well, since Rails is a framework, you've pretty much got the manual for how to use it.
I think the metaphor is applicable :)
@@mixandgo well, in that case you don't need to know how Rails is built. But I can't imagine someone's gonna have a fun time trying to build Rails apps without knowing what a class method is. And it's a PITA to read documentation without understanding what "accepts a block and yields x to it" means.
@@em_the_bee you are perfectly right. But guess what. The curiosity/frustration keeps you motivated to learn.
It's a way of discovering through practice.
1:25 damn interesting point thanks!
"Learning about computer science " be more specific ,what exactly?
Thanks friend.