Asking someone to learn a brand new framework/language in a week as part of a job interview is pretty harsh.
Ruby on Rails in a week
31–40 of 176 posts
Re: Ruby on Rails in a week
#32> For example, take the idea of inheritance. Low level thinking might sound like, “All the other classes are adding > But high level thinking might be more like, “I need to access the ApplicationController class’ methods. Ruby supports inheritance, so I’ll add I don't think this is "high level" vs "low level" thinking. Both are just different approaches to discovering the same thing. It's akin to learning guitar thro…
The difference is in the “it throws an error” bit- if you’re including lines of code because it makes your program work but you don’t know why, you’re also potentially introducing side effects and other behaviours that you don’t understand, which will bite you later.
Re: Ruby on Rails in a week
#33Asking someone to learn a brand new framework/language in a week as part of a job interview is pretty harsh.
Most companies will hire a smart person and give them the time to ramp up on the job... I had to learn 3 languages at my very first backend job. They hired me because I was smart. It took me over a month to get fully onboarded and that was their expectation.
Re: Ruby on Rails in a week
#34Asking someone to learn a brand new framework/language in a week as part of a job interview is pretty harsh.
That's actually exactly the kind of skill I'd look for in a new hire. I don't care which crunchy items you list on your resume so much as your ability to learn and integrate new technical information quickly (as well as a host of other skills, of course).
That said, learning a new thing does take a lot of time, so if I were asking a person to do that I would either commit to hiring them if they complete the learning challenge, or pay them for their time spent that week.
Re: Ruby on Rails in a week
#35Rails is in a really good place. When I learned it back in 2015 there were so many resources for learning, it felt like every time I had a specific problem related to a feature I was implementing there was either a railscasts or gorails video on it, along with 10 blog posts and stack overflow results. I can only imagine how much better it is now. It has been one of the only semi-modern learning experiences where I wa…
> It's definitely noticeable when you try to learn a newer framework with a much smaller community and less opinions. You could end up Googling for what you might think is a common thing to solve only to find zero answers in sight I have felt this exact way when I'm Googling for problems running Rails in modern cloud environments. It seems like there are loads of problems that are largely unsolved in the community at…
that seems beyond the scope of rails itself. why would you want to complicate deployment as a newbie? what problems are you facing that containerization specifically solves for you, rather than deploying to a (virtual) server directly? and why not heroku to start?
Re: Ruby on Rails in a week
#36Having picked up Rails 9 years ago and having been using it literally daily ever since, it's joyful to read from someone that is just starting. I also started with https://www.railstutorial.org/book , highly recommend it. I also loved Metaprogramming Ruby (Paolo Perrotta) - it's more advanced and starts to open your mind to how Rails magic DSL's were built. I just bought today "Rebuilding Rails" ( https://rebuilding-…
Love the Rebuilding Rails concept! I'm doing a very similar thing in Ruby, focused more on "web application development from first principles" ( https://theodorekimble.ck.page/e0bb43b156 ). I know I better absorb concepts if I can trace them back to a more fundamental "truth". Curious to hear if anyone else has found success with Rebuilding Rails, and what they found most helpful.
If you want to do the same thing (build up from 1st principles) with CSS, I ravingly endorse Axiomatic CSS as defined and implemented in https://every-layout.dev
Disclaimers: no affiliation, just a very satisfied customer. IME the free content alone is illuminating, and having paid $100 to access to the full "book" incl all the layouts' implementation it was a bargain.
Re: Ruby on Rails in a week
#37I love rails, but despite its presense for over a decade, it doesn't feel mature.
Something as basic as a native left join in ActiveRecord wasn't added until Rails 5.0, on June 30, 2016.
Something as basic as native multiple database support wasn't released until Rails 6.0, on August 16, 2019, 15 years after its initial release...
These are just two examples.
Re: Ruby on Rails in a week
#38I love rails, but despite its presense for over a decade, it doesn't feel mature. Something as basic as a native left join in ActiveRecord wasn't added until Rails 5.0, on June 30, 2016. Something as basic as native multiple database support wasn't released until Rails 6.0, on August 16, 2019, 15 years after its initial release... These are just two examples.
I've worked with Rails for since 2005, I've never needed those features yet.
Re: Ruby on Rails in a week
#39Now that Rails has StimuluseReflex / ActionCable (which is kind of an additional learning curve), it's got some incredible potential. I was skeptical of WebPacker at first, too, but also have grown to love it.
Re: Ruby on Rails in a week
#40Asking someone to learn a brand new framework/language in a week as part of a job interview is pretty harsh.
That's actually exactly the kind of skill I'd look for in a new hire. I don't care which crunchy items you list on your resume so much as your ability to learn and integrate new technical information quickly (as well as a host of other skills, of course). That said, learning a new thing does take a lot of time, so if I were asking a person to do that I would either commit to hiring them if they complete the learning…
> That's actually exactly the kind of skill I'd look for in a new hire. I don't care which crunchy items you list on your resume so much as your ability to learn and integrate new technical information quickly (as well as a host of other skills, of course).
Of course, but asking someone to spend a lot of hours on this in a week, with no guarantee of a job at the end of it is not a direction this industry needs to go. People have full time jobs, and parenting/carer/community responsibilities.
I was hired for a job a couple of years ago which required a lot of work on a new framework I had never touched before, and rather than the interview being around the framework, they gave me a month of full time employment to get up to speed - on the understanding that if it just wasn't clicking then we would both walk away with no hard feelings.