Ruby on Rails

On 4 February 2015 at 20:57, Justin Cheeze <lists@ruby-forum.com> wrote:
> Colin Law wrote in post #1167687:
>> On 4 February 2015 at 20:18, Justin Cheeze <lists@ruby-forum.com> wrote:
>>>> I posted a link in my previous message to a guide that should help you
>>>> debug the application. Also if you are being directed about which
>>>> version of rails to use and so on, is there not someone there who can
>>>> help you with debugging?
>>>>
>>>> Colin
>>>
>>> @Colin. My apologies for not addressing the forum properly.
>>>
>>> I have no idea how to reference the url sent with the application I'm
>>> working on.
>>
>> Sorry, no idea what you mean by that.
>>
>>>
>>> No, one senior dev got fired, just a few weeks ago. Another loved
>>> working his own hours beside conforming to the 9-5. Therefore, there is
>>> a senior dev ops dev who doesn't like helping out, but is lead at the
>>> moment until we get a senior dev in a few weeks. So, I'm fucked pretty
>>> much, as the tickets which have been assigned to me are mostly small
>>> markup and cascading changes, but this is deeper, the one I'm reaching
>>> out for help on.
>>
>> How are you getting on with rails guide that I posted the link for?
>> http://guides.rubyonrails.org/debugging_rails_applications.html
>>
>> Also I suggest you take time out to work right through a good tutorial
>> such as railstutorial.org (which is free to use online) that will show
>> you the basics of rails and while doing it you will find out about
>> debugging also as you track down the typos you made and work through
>> the exercises.
>>
>> Colin
>
> looked at the url, and was like how am I supposed to reference this with
> what I'm doing, and beat my head against the wall.

Let me ask a question. Do you understand (mostly) the code that you
are trying to fix? That is do you understand the basic flow through
it and what each section of the code does? At least the part that is
giving problems.

If you do understand it then the next task is to find out which bit is
failing. One easy way to start this is just to insert puts or inspect
commands in the ruby, to show where the code is and what the value of
variable is, the results of this will be printed in the server log
when it is executed. Then you can study that log and try to work out
what is going on.

If the above does not make sense then I am afraid you need to go on
some sort of training course or spend some time working through books
and stuff, in order that you get to the stage of understanding what I
am talking about.

If you do not understand the basic flow in a Rails app then as I said
take some time out (probably a week or so) and work right through that
tutorial. In the long run it will be time well spent. You are just
wasting your employers money banging your head against a brick wall
because of a fundamental lack of understanding of what you are trying
to do.

Colin

>
> yes, I remember you reaching out once before regarding a post I posted
> on the ruby forum. been trying to work on rails tutorial actually.
>
> again, many thanks for reaching out.
>
> --
> Posted via http://www.ruby-forum.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+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/20358479cca97c15c739ffa3d81e863e%40ruby-forum.com.
> For more options, visit https://groups.google.com/d/optout.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLv5H02hmOn9Vr4Be6v9_aUpMhqdZn%2Bqoj%2B%2Bqsr6uKy8AA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.