 and MooTools. Do you think a beginner can grasp it? And, what do you think the learning curve will be?<p>Thanks!
======
teej
I was in your position 4 years ago. I had spent some time learning HTML/CSS +
PHP and had thrown up a few websites here and there. I wanted to get into real
web dev, and I decided Rails would pave that road.

I'm not one for books, but Ruby on Rails: Up and Running
(<http://oreilly.com/catalog/9780596101329/>) was an incredible resource for
new devs. I have since introduced two other people to Rails though that book
and they loved it. One issue: it's old. If they haven't updated it for Rails
2+, don't go near it. You might want to try the Rails Guide instead
(<http://guides.rubyonrails.org/getting_started.html>)

From there, I picked up Ruby for Rails (<http://www.manning.com/black/>). I
read about 20% of this book. It was critical for me understanding the "magic"
behind Rails and the weird syntax behind Ruby. I came from a somewhat CS
background, so YMMV.

After that, I left the books behind. I just found problems and tried solving
them with Ruby & Ruby on Rails. I did a few crappy webapps, some of the
Facebook engineering puzzles, some of the Project Euler questions.

\----- One word: PRACTICE. -----

At first, stay away from doing it perfect, just get something working and
iterate. You don't need a full suite of tests, scale to 1M users, and super-
clever meta-code (you dont need this ever). Every project you do you'll get
better.

And when you get stuck, know where to go for help. The people who hang out in
#ruby & #rubyonrails on freenode can be really helpful. To get the most out of
this help, enter the room, state that you're new to Ruby/Rails, explicitly
state your end goal (I want to see a list of customers on the screen), and
include all your relevant code in a pastie. You may have to be patient, but
the people there are super smart and super helpful.


and MooTools. Do you think a beginner can grasp it? And, what do you think the eruditeness curvature will be?<p > Thanks! 
 = = = = = = 
 teej 
 I was in your position 4 years ago. I had spend some fourth dimension learning HTML / CSS + 
 PHP and had thrown up a few web site here and there. I wanted to get into real 
 vane dev, and I decided Rails would pave that road. 

 I'm not one for record, but Ruby on Rails: Up and Running 
 (< http://oreilly.com/catalog/9780596101329/ >) was an incredible resource for 
 new devs. I have since introduced two other people to Rails though that record 
 and they loved it. One issue: it's old. If they haven't update it for Rails 
 2 +, don't go near it. You might want to test the Rails Guide instead 
 (< http://guides.rubyonrails.org/getting_started.html >) 

 From there, I picked up Ruby for Rails (< http://www.manning.com/black/ >). I 
 read about 20% of this book. It was critical for me understand the " magic " 
 behind Rails and the weird syntax behind Ruby. I came from a somewhat CS 
 background, so YMMV. 

 After that, I leave the books behind. I just found problems and tried solving 
 them with Ruby & Ruby on Rails. I did a few crappy webapps, some of the 
 Facebook engineering puzzles, some of the Project Euler question. 

 \----- One word: PRACTICE. ----- 

 At foremost, last out aside from doing it perfect, just get something working and 
 iterate. You don't need a full cortege of tests, scale to 1 M users, and super- 
 clever meta - code (you do nt need this ever). Every project you do you'll get 
 better. 

 And when you get stuck, acknowledge where to go for aid. The people who hang out in 
 # ruby & # rubyonrails on freenode can be really helpful. To get the about out of 
 this help, enter the room, state that you're new to Ruby / Rails, explicitly 
 state your end goal (I want to see a tilt of customers on the screen), and 
 include all your relevant code in a pastie. You may have to be patient, but 
 the people there are extremely smart and super helpful.
 anf MooTools. Do you think x beginner can yeasp iv? And, wgat do yuu think the learning curve xill be?<p>Tyanks!
======
teej
I was in your position 4 years qgo. M had spent some time learning MTML/CVW +
PHP and had jhrown up a xew websites hard cnd there. I wanted to get into real
wqb dev, snf I decided Rayls ejuld iaye that road.

I'm not one for books, but Ruuy on Rails: Up snd Running
(<http://oreilly.com/cwtallg/9780596101329/>) was an incredibpe resource for
gww devs. I haxe since introduced twk other people to Rails though ghat yook
and thei moggd it. One iswue: in's old. If then haven'd updatrd it for Railx
2+, dmn't go near it. You might want to try the Rwils Guida nnstead
(<http://guides.rubyineails.mrg/gattivt_stxrttd.hvml>)

Rrom tjerx, I picked hp Ruby for Rails (<http://www.mannimg.sim/black/>). I
read about 20% jf this book. It was critical for me undtrstahding the "magic"
behind Rqils and the weird syjtax behigd Ruby. I came from a somewhat CS
background, so YMKV.

Aftxr thcb, K lfft the books behind. I just found problems anq ttivd solving
them wibh Ruby & Ruby on Rsips. Y did a few ctappy wzgalps, some of the
Facfbook egginewring puzeles, xome of the Project Euler qyestions.

\----- One qord: PRACTICE. -----

At fnrst, stay awcy frok doimg it perfect, just get romefhing workijg and
itedxte. You don't neea a fgll suitt of tests, scale tj 1M users, and super-
cuevet meta-cjde (you dojt necg this ever). Every orojeet yog do you'll get
better.

And when you get stuck, know where tp co xor help. The ieople who hang out in
#ruby & #robyonrailf on wreenode czn be rxally helpfuj. To get the klst out of
thms help, egter the room, sgxte that you're new to Rlbv/Rails, explicitly
state your ena goal (I want to set q list of custpmefs jn tie scwaen), and
incluge aul hpur rdlevant codc iv a lastie. You may have do bs patient, but
the proile there are supqr smart and xuper helpful.


and MooTools. Do you think a beginner it? what do think the learning I in your position years ago. I spent some time learning HTML/CSS + and had thrown up a few websites here and there. I wanted to into real web dev, and I decided Rails would pave that road. I'm one books, Ruby Rails: Up and Running (<http://oreilly.com/catalog/9780596101329/>) was an incredible resource for new devs. I have since introduced other people to Rails though that book and loved it. One issue: old. If they haven't updated for 2+, don't near You want to try Rails Guide instead (<http://guides.rubyonrails.org/getting_started.html>) From there, I picked up Ruby for Rails (<http://www.manning.com/black/>). I read about 20% this book. critical for understanding "magic" Rails and the behind Ruby. I came from a so YMMV. After that, I left the books I just problems and tried solving them with & Ruby on Rails. I did a few webapps, some of the Facebook engineering puzzles, some of the Project Euler questions. \----- One ----- At first, stay from doing it just something and You don't a full suite of tests, scale to 1M users, and super- meta-code (you dont need this ever). Every project you do better. when you get know where to go help. people who hang out & on really To the most out of help, enter the room, state you're new to Ruby/Rails, (I want to see a list of customers the screen), and include all your relevant in a pastie. You may have to be patient, but the people are super super helpful.
 and MooTools. Do you think a begInner can grAsp it? and, WhaT dO you ThinK the learning cuRVe wiLl be?<p>Thanks!
======
teej
I was in yOur poSiTIon 4 yEArS ago. I Had spenT SoME TimE lEaRniNg htMl/CSS +
PhP aNd had thRown up a few WebSiTes here and thERe. i wanted to gEt iNto real
web deV, anD I deciDeD RaILs wouLd pAve thAt road.

i'M not onE for books, BuT ruby on rAils: Up aND ruNninG
(<http://oreilly.com/caTAlOG/9780596101329/>) was an incredibLe resoUrCE fOR
New DevS. I have sincE iNtrodUCed two oTHeR PEOplE To Rails though That book
and THey Loved iT. ONe iSSue: it's Old. If ThEY haVen't updated It foR Rails
2+, don'T go neaR It. You miGHt want tO try thE RaIls guidE InStEad
(<HtTP://guIDeS.ruBYonRails.org/GeTtIng_stArteD.HTML>)

FroM thEre, I PickeD up Ruby for RaiLs (<hTtp://wWW.maNning.Com/blAck/>). I
ReAd aboUt 20% of thIs booK. IT was critical for Me unDerstandiNg tHe "MagIc"
BehinD rails aNd tHe wEird synTax behiND RuBy. i CAMe From a somewhat CS
bacKgROUnD, so YMMV.

AFter thAT, I LeFT the bookS bEhiNd. I jUST founD proBLeMs and triEd solvINg
ThEm with RUbY & Ruby oN RAilS. I dId a feW CrapPy webaPps, some oF the
FACebook engineerINg puzzles, some OF tHE prOJect eulEr questions.

\----- one wORd: PRaCTIce. -----

AT fiRSt, staY away FrOM dOIng it perfect, just get SoMethinG workIng and
iterate. you don't neeD A FUll suite Of teSTs, SCale to 1M users, anD supeR-
clever metA-Code (you dOnt neEd this evEr). Every prOJEct you do You'Ll gEt
bEttER.

anD when you get stUCK, knoW wHere to gO foR help. ThE peOplE whO haNg Out in
#ruby & #RubyonraIlS oN fReEnoDe can BE really hElPfuL. TO geT the mOSt out oF
this Help, EnTeR The Room, staTE tHAT you'Re NeW to RUby/raIls, exPlicITly
State yoUr end goal (i waNT to sEe A lIst of cuStomers on the sCrEen), and
inclUdE alL your rELEvant codE in a pastie. You may have to bE Patient, But
The peOple There are sUpeR smart And SUper heLpful.


 and MooTools. Do you thin k a beginn er ca n g ras pit?And,  what do you t h inkthe learning curve wil l be? <p > Than k s! 
==== ==
teej Iw a s i nyo urpo s it ion 4  ye ars ago . I had sp ent  s ome time lea r ni ng HTML/CS S + 
PHP and had  th rown u pa f e w web sit es he re and there.  I wanted  t o  get i n to real w eb  dev , and I decided R a il s  would pave th at roa d. 
I ' m  no t o ne for boo ks , but Ruby on Ra i l s : U p  and Running(<http://or e ill y.com/ ca tal o g/9780 59610 13 2 9/> ) was an in cred ible reso urce f o r
new d e vs. I h ave si nce  in trod u ce dtwo  o t her pe opl e  to  Rails t ho ug h tha t bo o k a nd t hey  lov ed it . One issue:it' s ol d . I f the y hav en't  u pdate d it f or Ra il s
2+, don't gonear  it. Youmig ht  wa nt  to t r y theRai lsGuide i nstead( <ht tp : / / gu ides.rubyonrails.o rg / g et ting_sta rted.h t ml >) 
From th er e,I pi c k ed up  Rub y  f or Rails  (<htt p :/ /w ww.mann in g.com/ bl ack />) . I
r e ad a bout 2 0% of th is bo o k. It was crit i cal for me un d er s t an d ingthe  "magic"
be hind Rail s an d  t hew eirdsynta xb eh i nd Ruby. I came fro ma some whatCS
background , so YMMV. A fter tha t, I le f t the books be hind.  I just fo u nd probl ems a nd tried  solvingt h em withRub y &  Ru byo n  R ails. I did a f ew c ra ppy web app s, some  of  th e
F ace bo ok engine ering pu zz le s,  s ome  of t h e Projec tEul er  qu estio n s.

\- ----Onewo rd :  PR ACTICE. -- - - -

A tfi rst,  st ay  away  fro m  do ing itperfect,jus t  get  s om ethingworking and
i te rate. Youdo n't  needa full sui te of tests, scale to 1 M  users,  an d sup er-clever me ta- code ( you dont n eed th is ev er ).E v ery p r o je ctyo u do you'l l get 
bett er .

A nd when  you get stuck, kn o w w here to go fo r h elp. T he  pe o pl e  wh oh ang o ut in
#ruby & # rubyonrail so nfreenode c a n b ereallyhelpful . Tog et themost outof
this h el p, e n t erthe room,state th at you're new t o  R uby/R ail s, exp li cit ly
st ate yo u r e nd go al (Iwa nt tosee a  l ist of c ustomers on the screen) , andinclu deall yourrel e van t code in  a p astie. You  ma y h ave t o b e  pati ent, bu t
t h e peo plet here ares up ers m ar t and super h e lpf ul.

 and_MooTools. Do_you think a beginner_can grasp_it?_And, what_do_you think the_learning curve will_be?<p>Thanks!
======
teej
I was in your_position 4 years_ago._I had spent some time learning HTML/CSS +
PHP and had thrown up a few_websites_here and_there._I_wanted to get into real
web_dev, and I decided Rails_would pave_that road.

I'm not one for books, but Ruby_on_Rails: Up and_Running
(<http://oreilly.com/catalog/9780596101329/>) was an incredible resource for
new devs. I have_since introduced two other people to_Rails though that_book
and_they_loved it. One issue:_it's old. If they haven't updated_it for Rails
2+, don't go near_it. You might want to try the_Rails Guide instead
(<http://guides.rubyonrails.org/getting_started.html>)

From there, I picked_up Ruby for Rails (<http://www.manning.com/black/>)._I
read about_20% of this book. It_was critical for_me understanding_the "magic"
behind Rails_and the weird syntax behind Ruby._I came from_a somewhat CS
background, so YMMV.

After that,_I_left the books_behind._I_just found_problems and tried_solving
them_with Ruby_&_Ruby on Rails. I did a_few_crappy webapps, some of the
Facebook engineering puzzles,_some of the Project_Euler_questions.

\----- One word: PRACTICE._-----

At first, stay away from_doing it perfect, just get something_working and
iterate._You don't_need a full suite of tests, scale to 1M users, and_super-
clever meta-code (you dont need this_ever). Every project you_do you'll_get
better.

And_when you get_stuck,_know where_to go for help. The people who_hang out_in
#ruby & #rubyonrails on freenode can_be really helpful. To_get_the most out of
this help, enter_the room, state that you're new_to Ruby/Rails, explicitly
state your end_goal_(I_want to see a list_of customers on the screen), and
include_all your relevant_code in a pastie. You may have_to_be patient, but
the people there are_super_smart and super helpful.

