schruthensis wrote: I''m not a programmer. I''m a designer that learned Lasso, then PHP and now Ruby and Rails. I don''t think I''ll ever become a programmer as I always need to look things up and I still miss some basic understanding of programming. But maybe I''m wrong. After many years with HTML and CSS I write it more or less fluently so there might be some hope after all. Anyway, I recognize your thoughts.> 1) I don''t know RubyI feel this is essential in order to get deeper into Rails. Ruby is by far the easiest language I''ve encountered yet.> 2) A bad experience with ruby 1.8.6 p 230 (STILL!? the most prominent > link on the rails download page)This part has always been easy for me.> 3) Unstable documentationWow. So true. In my eyes a major problem or THE problem. Good documentation is key for someone like me, and people alike. In this respect I must give PHP manual credit. I also believe there is a problem with basic understanding of pedagogics. I feel that many programmers have a problem with that. They explain B but leave out A, if you see what I mean. Of course it''s a question of what level you''re on. But as I see it Ruby is so simple that it shouldn''t be that hard to add in the missing parts. Let me give you and example that I think proofs this. I''m stuck with a problem with PayPal and IPN verification. How come there are so many having problems and making recurring questions about this here when it''s a question of a few lines of code? I don''t get this. There must be something very wrong here. But then again, this not only restricted to Ruby or Rails. It''s a general problem. Then you have those who give you answers like "this is not Rails, this is a Ruby question" and just leaves you with that, very well aware that it''s a thin line between them. Or those you say "read the manual first before you ask" and so on. You probably recognize the type. Not very constructive.> 6) Difficult integration with existing technologies. > b) apache: a million steps (including fastCGI) and it still > doesn''t work. (I''d been using WEBRick)Try Litespeed. I can really recommend it. Good luck with Rails. -- 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 post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
justin.smestad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2008-Aug-24 19:16 UTC
Re: Giving up on Rails: programmer un-happiness
You see one of these posts every few weeks. Most the people have already said what needs to be said. The one additional thing is maybe you should look at getting a tutor for help? I know I have personally tutored a few people (with NO programming experience) and they continue to use rails everyday. IT wgot such a good response that I launched a site to help find a tutor in the community, called Rubyme http://www.rubyme.net On Aug 23, 5:26 am, Pål Bergström <rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> schruthensis wrote: > > I''m not a programmer. I''m a designer that learned Lasso, then PHP and > now Ruby and Rails. I don''t think I''ll ever become a programmer as I > always need to look things up and I still miss some basic understanding > of programming. But maybe I''m wrong. After many years with HTML and CSS > I write it more or less fluently so there might be some hope after all. > Anyway, I recognize your thoughts. > > > 1) I don''t know Ruby > > I feel this is essential in order to get deeper into Rails. Ruby is by > far the easiest language I''ve encountered yet. > > > 2) A bad experience with ruby 1.8.6 p 230 (STILL!? the most prominent > > link on the rails download page) > > This part has always been easy for me. > > > 3) Unstable documentation > > Wow. So true. In my eyes a major problem or THE problem. Good > documentation is key for someone like me, and people alike. In this > respect I must give PHP manual credit. > > I also believe there is a problem with basic understanding of > pedagogics. I feel that many programmers have a problem with that. They > explain B but leave out A, if you see what I mean. Of course it''s a > question of what level you''re on. But as I see it Ruby is so simple that > it shouldn''t be that hard to add in the missing parts. > > Let me give you and example that I think proofs this. I''m stuck with a > problem with PayPal and IPN verification. How come there are so many > having problems and making recurring questions about this here when it''s > a question of a few lines of code? I don''t get this. There must be > something very wrong here. But then again, this not only restricted to > Ruby or Rails. It''s a general problem. > > Then you have those who give you answers like "this is not Rails, this > is a Ruby question" and just leaves you with that, very well aware that > it''s a thin line between them. Or those you say "read the manual first > before you ask" and so on. You probably recognize the type. Not very > constructive. > > > 6) Difficult integration with existing technologies. > > b) apache: a million steps (including fastCGI) and it still > > doesn''t work. (I''d been using WEBRick) > > Try Litespeed. I can really recommend it. > > Good luck with Rails. > > -- > Posted viahttp://www.ruby-forum.com/.--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I spoke on the phone with Bill Walton, who wrote "Rolling with Ruby on Rails Revisited". In short, he got me going. MANY thanks, Bill! Also, I have downloaded Netbeans and I think that will do a very good job for me, so thanks to Justin for pointing me in the right direction there! And now, to programming! -- 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 post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---