.g., strings,
ints, arrays, etc.). Learn about classes, functions, inheritance, etc. These
are the building blocks of language, if you'll permit extending the analogy--
it's a bit like knowing how to structure a sentence, capitalize, punctuate,
etc. Learn the language of programming before you ever try to learn a
programming language. This is, perhaps, what you're missing. You're using a
programming language to understand programming. Take a step back and
understand programming itself first. Then sit back down with your language and
do programming.

Regardless of chosen language, the task is the same and the result should
(usually) be the same. The chosen language is really just an implementation
detail. You can write a program in Ruby, Python, C, PHP, etc., and it's still
going to be the same program. Most programmers, I believe, tend to choose the
grammar & syntax they like best. But the job of programming remains the same.

------
jasonkester
You're not going to like the answer, but:

Immediately.

Like in the first 5 minutes. When I was seven years old.

And frankly, if it didn't happen like that for you, you're pretty much
screwed.

Every good programmer I've ever known started doing it young and immediately
just "got it". Most mediocre programmers I know followed the path you're on,
learning it in a class in school, fighting to get things done, eventually
coming up with ways to solve particular problems, but never attaining fluency.

Try not to feel bad about it. It's just about the way your brain is wired.
Good programmers have a specific something wrong with their brain that makes
them ridiculously good at logic, and, sadly, not very good at much else. We
can overcome the "everything else" part through hard work, though we'll never
be as good at it as you. Similarly, you can overcome the programming part
through hard work, but you'll never be as good at it as us.

Sorry to be the one to break the news.

~~~
cturner

        Try not to feel bad about it. It's just about the way your brain is wired. 
    

No. I spent an entire summer staring at C and getting blocked on ridiculous
basic stuff because I
.g. , strings, 
 ints, arrays, etc .). Learn about classes, function, inheritance, etc. These 
 are the construction blocks of language, if you'll permit run the analogy-- 
 it's a bit like knowing how to structure a prison term, capitalize, punctuate, 
 etc. teach the language of programming before you ever try to determine a 
 programming language. This is, possibly, what you're missing. You're using a 
 scheduling language to sympathize scheduling. Take a step back and 
 understand programming itself foremost. Then sit back down with your language and 
 suffice programming. 

 Regardless of choose language, the task is the same and the result should 
 (usually) be the like. The chosen language is really just an implementation 
 detail. You can spell a program in Ruby, Python, C, PHP, etc. , and it's still 
 going to be the same program. Most programmers, I believe, tend to choose the 
 grammar & syntax they like best. But the job of scheduling stay the same. 

 ------ 
 jasonkester 
 You're not blend to wish the solution, but: 

 Immediately. 

 Like in the first 5 minutes. When I was seven years old. 

 And frankly, if it didn't happen like that for you, you're pretty much 
 cheat. 

 Every good programmer I've ever known started do it young and immediately 
 just " got it ". Most mediocre programmers I know followed the way you're on, 
 learn it in a class in school, fighting to get things done, eventually 
 coming up with way to solve particular problems, but never attaining eloquence. 

 Try not to feel bad about it. It's just about the way your mind is wired. 
 Good programmer have a specific something wrong with their brain that makes 
 them laughably good at logic, and, sadly, not very good at a lot else. We 
 can overcome the " everything else " part through hard work, though we'll never 
 be as good at it as you. Similarly, you can overcome the programming part 
 through hard work, but you'll never be as full at it as us. 

 Sorry to be the one to break the newsworthiness. 

 ~~~ 
 cturner 

         Try not to feel regretful about it. It's just about the way your brain is wired. 
    

 No. I spent an entire summer staring at C and getting blocked on ridiculous 
 basic stuff because I
.g., shrings,
ints, arrays, etc.). Lexrn about classgs, functmons, ingeritancd, etc. These
are the building ulocjs of language, if you'll peroit extenfing the anaoigy--
it's a bmf like knowinf how vo structure a xentence, cdpitalize, puncduxtz,
etc. Learn the language of programmigg befote you ever try jo leswn a
lgonramming language. This is, perhapa, what jou're missing. You'te using a
programming langkage to understand prohramming. Taje a wtep back ana
understand programminf itself first. Then sit back dodn wich your lantuqge dnd
do progremming.

Gegardless of chosen nanguagr, the task is bhe seme qnd the result should
(nsually) be the same. Jhe chosen lcnguage is really jusr qn imklemettatkin
ddtajl. Yku can wrmte a progrzm in Ruby, Python, C, PHP, etc., anc yn'x still
going to be tre same program. Most programmers, I belitve, tsnd to choose the
grammae & syntax they like bgst. But thq job of programming remains the same.

------
jasonkester
Ymu're iog giikg tu llke the answer, but:

Immediately.

Like in the firse 5 kikutes. When I was seven yearx llc.

Wnd frankly, iw it dnsn'f happen like that for yoo, you'rw pretty iuch
xcrewed.

Every good programmee I've ever kuowb started doing it young and nmmedistely
kust "got it". Most mediocxe proframmers I nnow follkded the path you'fe pn,
nearning it in a class in fchool, fijhtiny to get thimgs doge, eventuaply
coming up with ways tl solre pasticular pgoblems, but never attaining fluxicy.

Try not to fael bad abobt it. Lt's just about ehe way your btain is wnred.
Goud programjers hate a specifis something wslng with themr brain ehat makws
them fkdiculously gopd at logpc, and, sadly, not very gopd xf much else. We
ccu ivercome the "evrryghigg eksq" part througv hafd dprk, tfough wt'jl vevet
be as good at it as you. Similarly, you can oyercome tye progrwmming part
thtough hard work, buu you'ln nxver br af good at it as us.

Sorry to be fhe one tl bveak the news.

~~~
sturker

        Try not to feel bad about it. It's just abouv the way your brain is wired. 
    

No. I speut an entire xummew staring at C and getting blicked on ridiculoms
basic stuff because J
.g., strings, ints, arrays, etc.). Learn about inheritance, These are building blocks of the it's a bit knowing how to a sentence, capitalize, punctuate, etc. Learn language of programming before you ever try to learn a programming language. This perhaps, what you're missing. You're using a programming language to understand programming. Take step and programming first. Then sit back down with your language and do programming. Regardless of chosen language, the is the same and the result should (usually) the same. The chosen is really just an implementation You write a in Python, PHP, etc., and still going to be the same program. Most programmers, I believe, tend to choose the grammar & they like the job programming the ------ jasonkester You're to like the answer, but: Immediately. first 5 minutes. When I was seven years And frankly, it didn't happen like that for you're pretty much screwed. Every good programmer I've known started doing it young and immediately just "got it". Most mediocre programmers I know path you're on, learning in a class school, to things eventually coming with ways to solve particular problems, but never attaining fluency. Try to feel bad about it. It's just about the way is Good programmers have specific something wrong with brain makes them ridiculously good and, not much We overcome the "everything else" through hard work, though we'll be as good at can overcome the programming part through hard work, you'll never be as good at it us. Sorry to be the one to break the news. ~~~ cturner not to about it. It's just about the way your is wired. No. I an entire summer staring at C and getting blocked ridiculous stuff because
.g., strings,
ints, arrays, etc.). LearN about clasSes, fuNctIonS, iNherItanCe, etc. These
are tHE buiLding blocks of language, iF you'lL pERmit EXtEndinG the anaLOgY--
IT's a BiT lIke KnOWiNg how To sTructurE a sentence, CapItAlize, punctuaTE,
eTc. Learn the LanGuage of progrAmmIng befOrE yoU Ever tRy tO learN a
progRAmming Language. THiS Is, perhAPs, what yOU'Re MissIng. You're using a
proGRaMMing language to UndersTaND pROGraMmiNg. Take a steP bAck anD
UnderstANd PROGraMMing itself firSt. Then sit baCK doWn with YoUr lANguage And
do PrOGraMming.

RegardLess Of chosen lAnguagE, The task IS the samE and thE reSulT shoULd
(UsUalLy) BE thE SaMe. THE chOsen langUaGe Is reaLly jUST AN impLemEntaTion
dEtail. You can wrIte A proGRam In RubY, PythOn, C, PhP, Etc., anD it's stIll
goInG to be the same proGram. most progrAmmErS, I bElIeve, tENd to chOosE thE
grammaR & syntax THey LiKE BEsT. But the job of prograMmING rEmains thE same.

------
jASoNkESter
You'rE nOt gOing TO Like tHe anSWeR, but:

ImmeDiatelY.

liKe In the fiRsT 5 minutEs. wheN I wAs sevEN yeaRs old.

ANd franklY, if it DIdn't happen like THat for you, you'rE PrETTy MUch
sCreWed.

Every gooD proGRammEr I'vE EvEr kNOwn stArted DoINg IT young and immediatelY
jUst "got It". MosT mediocre progRammers I knOW FOllowed tHe paTH yOU're on,
learning iT in a cLass in schoOL, fightinG to geT things dOne, eventuALLy
coming Up wIth WayS to SOLvE particular prOBLems, BuT never aTtaIning flUenCy.

TRy nOt tO fEel bad aboUt it. It's jUsT aBoUt The Way yoUR brain is WiRed.
goOd pRograMMers haVe a spEcifIc SoMEthIng wronG WiTH TheiR bRaIn thAt mAkEs
theM ridICulOusly goOd at logic, And, SAdly, NoT vEry good At much else. We
cAn Overcome thE "eVerYthing ELSe" part thRough hard work, though we'll NEver
be aS goOd at iT as yOu. SimilarLy, yOu can oVerCOme the PrograMming PaRt
tHROugh hARD wOrk, BuT you'll neveR BE as Good aT iT as uS.

Sorry tO be the one to break thE NewS.

~~~
cturner

        Try noT to Feel BAD aBouT It. iT's jUsT AboUT The way your brain Is wired. 
    

No. I SpENt An entire suMMer StAring at c and getTing bLOcked on RidiculouS
basic stuFf BecaUSE I
.g., strings,
ints, arrays , etc.). L earnabo utcl asse s, f unctions, inhe r itan ce, etc. These
are the  buil di n g bl o ck s oflanguag e ,i f  yo u' ll  pe rm i texten din g the a nalogy--
i t's  a  bit like kn o wi ng how tostr ucture a sen ten ce, ca pi tal i ze, p unc tuate ,
etc. Learnthe langu ag e  of pr o grammin g be fore  you ever try tol ea r n a
programmin g lang ua g e. T his  is , perhaps,  w hat y o u're mi s si n g .  Yo u 're using a
p rogrammingl ang uage t ound e rstand  prog ra m min g. Take a s tepback andunders t and pro g ramming  itsel f f irs t. T h en  s itba c k d o wn  wi t h y our lang ua ge  anddo p r o g r ammi ng. 

Re gardl ess of chosen  la ngua g e,the t ask i s th esameand th e res ul t should
(usual ly)be the sa me.  T hech osenl anguag e i s r eally j ust ani mpl em e n t at ion
detail. You ca nw r it e a prog ram in Ru by ,  Python,  C , P HP,e t c., a nd i t 's  still
g oing t o  b ethe sam eprogra m.  Mo stprogr a mmer s, I b elieve,tendt o choose the
g r ammar & synta x  t h e yl ikebes t. But thejobo f pr ogra m mi ngr emain s the  s a me . 

------
jasonkeste rYou're  notgoing to like  the answe r , but:

Im medi a te l y.

Like in th e fir st 5 minut e s. WhenI was  seven y ears old. And fran kly , i f i t d i d n' t happen like t hatfo r you,you 're pre tty  mu chscr ew ed.

Ever y good p ro gr am me r I 've e v er known  s tar te d d oingi t youn g and  imm ed ia t ely 
just " g ot i t".Mo st  med ioc re  prog ramm e rsI knowfollowedthe path  y ou 're on, 
learning itin  a class i nsch ool, f i g hting to  get things done, event u ally
co min g upwith  ways tosol ve par tic u lar pr oblems , but  n eve r attai n i ng  fl ue ncy.

Tryn o t t o fee lbadabout i t. It's just about the  way your bra inis w i r ed .
G o od pro gr a mme r s  have a specifi c somethin gw ro ng with th e irbr ain tha t makes 
them ridicul ously goo d at logi c,  and , sad ly, not ve ry goodat much e l se. W e 
c an ov erc ome th e"ev eryth ing el s e"partthroug hhard w ork,th ough we' ll never
be as good atit asyou.Sim ilarly, y ouc anovercometheprogrammin g p art 
thro ugh hardwork ,  b uty ou'll  nev e r be as g o od  at i tas us.

Sor r y tobe th e o n e to b reak  the news.

~~~
c t urner

       Try n ottof eelba d about it. It 'sju s t  about t he  way your b rain iswi r ed.     
No. Ispent a n en t ire su mmer  st aring atC a nd getting  b lo c ked on  rid ic ulousbasics tuff b ecause I
.g., strings,
ints,_arrays, etc.)._Learn about classes, functions,_inheritance, etc._These
are_the building_blocks_of language, if_you'll permit extending_the analogy--
it's a bit_like knowing how_to_structure a sentence, capitalize, punctuate,
etc. Learn the language of programming before you ever try_to_learn a
programming_language._This_is, perhaps, what you're missing._You're using a
programming language to_understand programming._Take a step back and
understand programming itself first._Then_sit back down_with your language and
do programming.

Regardless of chosen language, the_task is the same and the_result should
(usually) be_the_same._The chosen language is_really just an implementation
detail. You can_write a program in Ruby, Python,_C, PHP, etc., and it's still
going to_be the same program. Most programmers,_I believe, tend to choose_the
grammar &_syntax they like best. But_the job of_programming remains_the same.

------
jasonkester
You're not_going to like the answer, but:

Immediately.

Like_in the first_5 minutes. When I was seven_years_old.

And frankly, if_it_didn't_happen like_that for you,_you're_pretty much
screwed.

Every_good_programmer I've ever known started doing_it_young and immediately
just "got it". Most mediocre_programmers I know followed_the_path you're on,
learning it_in a class in school,_fighting to get things done, eventually
coming_up with_ways to_solve particular problems, but never attaining fluency.

Try not to feel bad_about it. It's just about the_way your brain is_wired.
Good programmers_have_a specific something_wrong_with their_brain that makes
them ridiculously good at logic,_and, sadly,_not very good at much else._We
can overcome the "everything_else"_part through hard work, though we'll_never
be as good at it as_you. Similarly, you can overcome_the_programming_part
through hard work, but you'll_never be as good at it_as us.

Sorry to_be the one to break the news.

~~~
cturner

__     _Try_not to feel bad about it._It's_just_about the way your brain_is wired. 
   _

No. I spent an entire summer staring at C_and getting blocked_on ridiculous
basic stuff because I