Hey Jason,
Thank you for the book recommendation, a good addition to what I have
so far with books on Rails and Ruby. I have gone through many of the
sections of the Rails guide and the edge version. The drill down that
approach that Walter described is something I'm doing, but now I'm just
trying to find the point of origin with each gem/module. So much magic,
hard to tell when you hit paydirt. As for Ruby itself, I've explored it
regularly for a while now, just feel like it sticks when I need to use the
information. Thank you again for the recommendations, much obliged.
On Monday, August 12, 2019 at 10:05:58 AM UTC-5, te...@datatravels.com
wrote:
>
>
> I think perhaps one of the things you may be up against is that this
> learning curve is actually very out-dated now.
>
> It's an old book, but this was one of the most popular books from
> 2007-2009 when a lot of us were learning the basics of Rails you are asking
> about here.
>
>
> https://www.thriftbooks.com/w/agile-web-development-with-rails-a-pragmatic-guide_dave-thomas_david-heinemeier-hansson/313251/?mkwid=sHKLUDuV1%7cdc&pcrid=70112900832&pkw=&pmt=&plc=&pgrid=21329340912&ptaid=pla-293510751240&gclid=CjwKCAjwnMTqBRAzEiwAEF3ndnLhRREJENrkPly581-PMj-QFOLuzmC2IBUYrUtYbVHYpfSeM3hqCRoCalUQAvD_BwE#isbn=097669400X&idiq=2753678
>
>
> It might reference some things in older version of Rails but the basics of
> what you are asking are thoroughly covered in the MVC pattern.
>
> The Rails documentation can be difficult, but have you been through the
> Rails Guides? I would recommend working your way through the Rails Guides
> one by one and typing out the examples in your editor to learn what each
> piece of code does.
>
> You're right, developers can write docs with too many assumptions and not
> enough explanation. But nothing substitutes good old fashioned trial &
> error.
>
>
> Finally, I would strongly recommend you start with a solid foundation of
> Ruby, as I know many people who tried to learn Rails before Ruby and got
> lost.
>
> Good luck
>
>
> Jason
>
>
>
> > On Aug 7, 2019, at 10:15 PM, Noel <noel...@gmail.com <javascript:>>
> wrote:
> >
> > You just hit everything that I was trying to figure out and then some.
> This is what I’ve been needing to know(I can’t be certain of the that).
> Last question, how did you figure that out?; because that’s where this is
> kind of embarrassing, that I’ve held out to ask this for so long for fear.
> I’m sure intuition and experience comes with understanding what’s under the
> hood, but how does a junior dev figure stuff out like this? Please be
> merciful, don’t say look at the documentation, the documentation needs
> documentation. The documentation is not very clear for a junior dev because
> some stuff is abstracted and it’s like you have to be in the know about
> some other concept(that is omitted because reasons) that isn’t mentioned
> but understood.
> >
> > Goes without saying but thanks man, this is solid knowledge I can use.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Ruby on Rails: Talk" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to rubyonra...@googlegroups.com <javascript:>.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-talk/cec8887e-7b38-4feb-b403-ef2810038a84%40googlegroups.com.
>
>
>
>
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-talk+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/a9244437-184c-4b73-ac77-595f3730ac39%40googlegroups.com.
