 in the hands. When I learn a new programming language
it's total chaos for 1-2 weeks and then the new regime settles and I can
understand what I have been doing. After half a year of being exposed to a new
programming language even more of the teachings settle and I can begin
understanding more, but programming it's a practical art. I suppose it can be
different if you are more mathematically minded than I am.

I suggest doing ALL the exercises in a programming book - as fast as you can
without trying to really understand what is going on behind the scenes. The
secret is that you don't have to really understand what the hell is going on
behind the scenes, you just have to know enough to stay out of trouble and
that knowledge comes from experience. In the beginning of a programming career
it'll be impossible to guess what weird bugs might occur so just code and see
what happens.

In short, _you have to have a lot of practical knowledge of programming to
support your theoretical knowledge_, otherwise you cannot do anything with
either. A chicken and egg situation, so it's best just to jump into the deep
waters and try to swim to the surface.

------
ajuc
I've got C64 and manual in German when I was 10 (I've only knew Polish at that
time, but who cares :)).

For a few years I only played games, and sometimes entered some example BASIC
code and tinkered with constans in code to see what will happen. I remember
that my copy of manual had error in some magic graphic system initialization
code, so I've never programmed graphic on C64. It was very frustrating.

Then I've got PC when I was 15 and I played with Turbo Basic, then Turbo
Pascal - then I've understood variables and it all started to make sense.
Since then I only feel like I know less, and less :)

PS - the most impressive thing I've seen that encuraged me to keep programming
was ASCII art adventure game written in windows batch files. I've thought - if
someon can do so much witch bat files, I can do everything with my knowledge
of Turbo Pascal :)

------
thibaut_barrere
Even once you can write code on your own, things are painful from times to
times, and I believe that's normal and a
in the hands. When I learn a new programming linguistic process 
 it's entire chaos for 1 - 2 weeks and then the new regime decide and I can 
 understand what I have been doing. After half a class of being exposed to a new 
 programming speech even more of the teachings settle and I can get down 
 understanding more, but programming it's a practical art. I presuppose it can be 
 different if you are more mathematically minded than I am. 

 I suggest doing ALL the exercises in a programming record - as fast as you can 
 without trying to really sympathize what is going on behind the scenes. The 
 mystery is that you don't have to actually understand what the sin is going on 
 behind the scenes, you just have to sleep together enough to stay out of trouble and 
 that knowledge comes from experience. In the beginning of a scheduling career 
 it'll be impossible to think what weird bugs might occur so just code and see 
 what happens. 

 In short, _ you have to suffer a lot of practical cognition of scheduling to 
 support your theoretical knowledge _, otherwise you cannot do anything with 
 either. A wimp and egg site, so it's best just to leap into the deep 
 waters and try to swim to the surface. 

 ------ 
 ajuc 
 I've got C64 and manual of arms in German when I was 10 (I've only knew Polish at that 
 time, but who cares :)). 

 For a few years I only played game, and sometimes accede some example BASIC 
 code and tinkered with constans in code to see what will find. I remember 
 that my copy of manual had error in some magic graphic system initialization 
 code, so I've never programmed graphic on C64. It was very frustrating. 

 Then I've get PC when I was 15 and I bet with Turbo Basic, then Turbo 
 Pascal - then I've understood variables and it all start to make common sense. 
 Since then I only feel like I know less, and less :) 

 PS - the most impressive matter I've seen that encuraged me to keep programming 
 was ASCII artwork adventure game written in windows batch files. I've thought - if 
 someon can do so much witch bat files, I can do everything with my knowledge 
 of Turbo Pascal :) 

 ------ 
 thibaut_barrere 
 Even once you can publish code on your own, things are painful from multiplication to 
 times, and I believe that's normal and a
 in the hands. When I learn x new programmiut langnage
it's total cfaos for 1-2 weeks and then the nww retime settles and I can
jnderstanf what I havt been doing. Aftec half a year kn beiug exposed to a kew
programmhng language eeev lore of the teachings settle and I san begon
knderstanding iore, fut lgonramming it's a practical art. I shppose pt can be
differeny if you are more mathematlcalpy minded than I al.

I suggest eoind ALL the exefcises in a programminf book - as fast as you can
withojt trving to reaolt ujgerstand whet is doing on behlmd the scenes. The
secret is bhat bou eon't have to really uiderstand what the hgll is goitg on
behind the scebew, you jusd haxw tu khox ehough ho atay out or trouble abd
that knowledge cokef from experiehce. In tre beginning of a programming career
it'ln bs impossible to guess wyat weird bugs might lccur so tust code and see
what happens.

In short, _you have to have x lit ud oractical knowledge of programming to
support rkut nheoretical knowlcdge_, otherwise you cwnmjt do anythine with
zjtger. A chicken and fgg sitoation, so it's btst jist to jump into the deep
warers and try ro swim to the suryace.

------
ajuc
I've yot C64 snd msnual in German when I cas 10 (I'be only knea Polish zg that
time, but wfo barev :)).

For a few years I only pjayed gamxs, anb sometioes gntered some examole BASIC
code and tinkerfd wijh convtans in clde to see what will happen. I rxkember
that mi cmpy of manucl had error in somq magic graphie system initkalization
bode, so I'te never prodrammed graphhf on C64. It wav very fwusteatibg.

Then K'xe got PC when I was 15 aub I playee with Turbo Basic, thgn Turbo
Pascal - tktn U've understood farkabjed end ie all started to oakd sensd.
Since uken K onky feel like I know ness, and less :)

PS - the koft imprewsive thyng I've seen yhat encuraged me uo kee' progcamminb
waf ASCII art adventure game wriften in wlndjws batch fijes. L've jhought - if
xomeon can do so much witch bat files, I can do everything with my knowledge
oy Uurbo Pascal :)

------
vhibaue_barrere
Eeen once you can wrire code on your oen, things are painful from dimes to
times, and I believe that's normal and a
in the hands. When I learn a language total chaos 1-2 weeks and and can understand what have been doing. half a year of being exposed a new programming language even more of the teachings settle and I can understanding more, but programming it's a practical art. I suppose it can be if are mathematically than I am. I suggest doing ALL the exercises in a programming book - as fast you can without trying to really understand what going on behind the The secret is that you have really understand the is on behind the you just have to know enough to stay out of trouble and that knowledge comes from experience. the beginning programming career be to what weird bugs so just code and see what _you have to have a lot of practical of programming support your theoretical knowledge_, otherwise you do anything with either. A chicken and egg so it's best just to jump into the deep waters and try to swim to ------ ajuc I've got and manual in when was (I've knew Polish that time, but who cares :)). For a few years I played games, and sometimes entered some example BASIC code and constans code to see will happen. I remember my of manual had error magic system I've programmed on C64. It was frustrating. Then I've got PC I was 15 and then Turbo Pascal - then I've understood variables it all started to make sense. Since I only feel like I know less, and less :) PS - most impressive seen that encuraged me to keep programming was art adventure game written windows batch files. I've thought - if someon can so witch bat I can do with my knowledge Turbo Pascal :) Even once can code things are painful from times to and believe that's normal and a
 in the hands. When I learn a new pRogramming LanguAge
It's ToTal cHaos For 1-2 weeks and theN The nEw regime settles and I can
UnderStANd whAT I Have bEen doinG. afTER haLf A yEar Of BEiNg expOseD to a new
ProgramminG laNgUage even more OF tHe teachingS seTtle and I can bEgiN
underStAndINg morE, buT progRamminG It's a prActical arT. I SUppose IT can be
dIFFeRent If you are more matheMAtICally minded thaN I am.

I sUgGEsT DOinG ALl the exerciSeS in a pROgrammiNG bOOK - As fASt as you can
witHout trying tO ReaLly undErStaND what iS goinG oN BehInd the sceneS. The
Secret is tHat you DOn't have TO really UndersTanD whAt thE HeLl Is gOiNG on
BEhInd THe sCenes, you JuSt Have tO knoW ENOUgh tO stAy ouT of trOuble and
that kNowLedgE ComEs froM expeRienCe. in the BeginnIng of A pRogramming careeR
it'lL be impossIblE tO guEsS what WEird buGs mIghT occur sO just coDE anD sEE
WHaT happens.

In short, _you HaVE To Have a lot Of pracTIcAl KNowledge Of ProGramMINg to
sUppoRT yOur theorEtical KNoWlEdge_, othErWise yoU cAnnOt dO anytHIng wIth
eitHer. A chicKen anD Egg situation, so IT's best just to jUMp INTo THe deEp
wAters and try To swIM to tHe suRFaCe.

------
aJUc
I've Got C64 aNd MAnUAl in German when I was 10 (I'Ve Only knEw PolIsh at that
time, But who careS :)).

fOR a few yeaRs I oNLy PLayed games, and sOmetiMes entered SOme exampLe BASiC
code anD tinkered WITh constaNs iN coDe tO seE WHaT will happen. I rEMEmbeR
tHat my coPy oF manual Had ErrOr iN soMe Magic grapHic systeM iNiTiAlIzaTion
cODe, so I've nEvEr pRoGraMmed gRAphic oN C64. It wAs veRy FrUStrAting.

ThEN I'VE Got Pc wHeN I waS 15 anD I PlayeD witH turBo Basic, Then Turbo
pasCAl - thEn i'vE undersTood variables AnD it all starTeD to Make seNSE.
Since thEn I only feel like I know lesS, And less :)

pS - tHe mosT impRessive thIng i've seeN thAT encurAged me To keeP pRogRAMming
WAS AsCIi aRt adventurE GAme WrittEn In wiNdows baTch files. I've thought - IF
soMeon can do so muCh wItch BAT fIleS, i cAN do EvERytHINg with my knowledGe
of Turbo PAsCAl :)

------
Thibaut_barREre
evEn once yOu can wrIte coDE on your Own, things Are painfuL fRom tIMEs tO
times, and I Believe tHat's normaL And a
 in the hands. When I lear n a new pr ogram min g l an guag e
it 's total chaos for1-2 weeks and then the  newre g imes et tlesand I c a nu n der st an d w ha t  I  have  be en doin g. After h alf  a  year of bei n gexposed to  anew
programm ing  langu ag e e v en mo reof th e teac h ings s ettle and  I can be g in
unde r s ta ndin g more, but progr a mm i ng it's a prac ticalar t .I sup pos e it can b ediffe r ent ify ou a r e m o re mathematic ally minded tha n I am .
Is uggest  doin gA LLthe exercis es i n a progr amming book -a s fastas you  ca n
w itho u ttr yin gt o r e al lyu nde rstand w ha tis go ingo n b ehin d t he s cenes . The
secretisthat you  don' t hav e to  r eally  under stand  w hat the hell is  goi ng on
beh ind  t hesc enes, you ju sthav e to kn ow enou g h t os t a yout of trouble and 
t h a tknowledg e come s  f ro m  experie nc e.In t h e  begi nnin g  o f a prog rammin g  c ar eer
it' ll  be im po ssi ble  to g u esswhat w eird bug s mig h t occur so jus t  code and see wh a t  h a ppen s.
In short,_you have  toh av e a lot o f pra ct i ca l  knowledge of progr am ming t o
sup port your the oretical k n o w ledge_,othe r wi s e you cannot d o any thing with either.A chi cken and  egg situ a t ion, soit' s b est  ju s t  t o jump into t h e  dee pwatersand  try to  sw imtothe  s urface.
------
a ju cI' ve  go t C64 and manu al  in  G erm an wh e n I wa s 10(I'v eon l y k new Pol i sh a t th at 
t ime,  bu twho c ares :)) .

Fora few yea rsI  onl ypl ayed ga mes, and some ti mes entere dsom e exam p l e BASICcode and tinkered withc onstans  in  code  tosee whatwil l happ en. I reme mber
t hat m ycop y of ma n u al  ha derror in s o m e m agicgr aphi c syste m initialization
c o de,  so I've neve r p rogr a m me d g r ap h icon C64 . It was very fru strating.
T h en  I've gotP C w he n I was  15 and  I pl a yed wit h Turbo B asic, the nTurb o Pas cal - then  I've un derstoodv ariab l es  anditall st ar ted  to m ake se n se. 
Sinc e then  I  onlyfeelli ke I kno w less, and less :)

PS  - the  most  im pressivethi n g I 've seenthat  encuraged  me  to  keep  pr o gramm ingw as  AS C II ar t ad v enture ga m ewri t t en  in windows b a tch  file s.I 've th ough t - if
someon can do so much wit ch b a t  fi les ,  I c an  do everything  wi th m y knowle dg e
of TurboPascal : )----- -
thib aut_ba rrere
E v e no nce yo u ca n w rite code  on  y o ur own,  t hi n gs are  pai nf ul fro m time s  tot i mes, and I belie ve th a t 's no r mal  anda
 in_the hands._When I learn a_new programming_language
it's_total chaos_for_1-2 weeks and_then the new_regime settles and I_can
understand what I_have_been doing. After half a year of being exposed to a new
programming language even_more_of the_teachings_settle_and I can begin
understanding more,_but programming it's a practical_art. I_suppose it can be
different if you are more_mathematically_minded than I_am.

I suggest doing ALL the exercises in a programming_book - as fast as you_can
without trying to_really_understand_what is going on_behind the scenes. The
secret is that_you don't have to really understand_what the hell is going on
behind the_scenes, you just have to know_enough to stay out of_trouble and
that_knowledge comes from experience. In_the beginning of_a programming_career
it'll be impossible_to guess what weird bugs might_occur so just_code and see
what happens.

In short, _you_have_to have a_lot_of_practical knowledge_of programming to
support_your_theoretical knowledge_,_otherwise_you cannot do anything with
either. A_chicken_and egg situation, so it's best just_to jump into the_deep
waters_and try to swim_to the surface.

------
ajuc
I've got C64_and manual in German when I_was 10_(I've only_knew Polish at that
time, but who cares :)).

For a few years_I only played games, and sometimes_entered some example BASIC
code_and tinkered_with_constans in code_to_see what_will happen. I remember
that my copy of_manual had_error in some magic graphic system_initialization
code, so I've never_programmed_graphic on C64. It was very_frustrating.

Then I've got PC when I_was 15 and I played_with_Turbo_Basic, then Turbo
Pascal - then_I've understood variables and it all_started to make_sense.
Since then I only feel like I_know_less, and less :)

PS - the_most_impressive thing I've seen that encuraged_me_to_keep programming
was ASCII art adventure_game written in windows batch files._I've thought - if
someon can do so much witch_bat files, I_can do everything with my_knowledge
of_Turbo_Pascal :)

------
thibaut_barrere
Even once you can write code on your own,_things are_painful from times_to
times, and I believe that's normal and a