 researches, grabbed a related domain and
making a plan.

Learning Programming? Oups! I forgot about it!!!

------
CyberFonic
You need to design first - on paper, white-board, etc. You wouldn't build a
house without blueprints, so why try to write a big program without sketching
stuff out so that you can break down into manageable chunks.

If that doesn't help, then maybe you need to take a good CS course. If you
have only programmed in C++, then it doesn't sound like a comprehensive
background in CS.

~~~
jff
Exactly this. The image of the lone hacker sitting down and pouring out a
bunch of code straight from his brain is a romantic one, but if you haven't
spent a little time deciding what your data structures are going to look like
and how you're going to pass stuff around, etc., your code will be crap. "Just
coding it" leads to both frustration as you sit wondering what you should be
writing and why programming is so hard, and poor code. The poor code comes in
when you start throwing in stuff like one-use elements in your structs to keep
track of something you hadn't forseen, when a little bit of planning could
have alleviated that.

I'm certainly not saying you should go write up a design document complete
with UML and everything. That would be ridiculous, damn it I'm an engineer not
a bureaucrat! Just sit down and think (on paper) about how some of the
important stuff needs to look. It'll help a lot.

As for the second point, C++ does seem like a weird place to start. Go learn
assembly or C. Learning to write assembly is a process of continually solving
tiny programming puzzles, as you figure out how to hand-roll a loop and such.

------
wccrawford
I've been writing code 'on my own' since 4th grade. My school gave a class on
programming the Apple IIe and I loved it. My parents bought me a series of
computers, starting with a Sinclair 1000, and I wrote little programs for all
of them until they weren't good enough and we upgraded. I taught myself
several other forms of basic, then started on other languages like C, PHP and
Cold Fusion.

Maybe you need to stop 'learning
researches, grabbed a related domain and 
 making a design. 

 Learning Programming? Oups! I forget about it! !! 

 ------ 
 CyberFonic 
 You need to design inaugural - on newspaper, white - board, etc. You wouldn't construct a 
 house without blueprints, thus why try to write a adult program without sketching 
 material out so that you can break down into manageable chunks. 

 If that doesn't help, then maybe you need to take a full CS course. If you 
 have only programmed in C++, then it doesn't fathom like a comprehensive 
 background in CS. 

 ~~~ 
 jff 
 Exactly this. The image of the lone hack sitting down and pour out a 
 bunch of code straight from his brain is a amatory one, but if you haven't 
 spent a little time deciding what your data structures are going to look like 
 and how you're going to pass stuff around, etc. , your code will be crap. " Just 
 coding it " leads to both frustration as you sit wondering what you should be 
 spell and why programming is so intemperate, and hapless code. The poor code comes in 
 when you start project in stuff like one - use elements in your structs to keep 
 racetrack of something you hadn't forseen, when a little bit of planning could 
 have alleviated that. 

 I'm certainly not saying you should go compose up a design document complete 
 with UML and everything. That would be ridiculous, bloody it I'm an engineer not 
 a bureaucrat! Just baby-sit down and remember (on paper) about how some of the 
 important stuff needs to count. It'll help a lot. 

 As for the second point, C++ does seem like a weird place to start. Go teach 
 assembly or C. Learning to write fabrication is a process of continually solve 
 tiny scheduling puzzles, as you figure out how to pass - roll a loop and such. 

 ------ 
 wccrawford 
 I've been writing code' on my own' since 4th grade. My school give a class on 
 programming the Apple IIe and I loved it. My parents bought me a series of 
 computers, starting with a Sinclair 1000, and I wrote small programs for all 
 of them until they weren't good enough and we upgrade. I taught myself 
 several other forms of basic, then started on other lyric like C, PHP and 
 Cold Fusion. 

 Maybe you need to stop' learning
 redearches, grabbed a relattd domain and
makiut a plen.

Learnjng Progfamming? Oups! I forgot about mt!!!

------
CyverFobic
You need to design wirst - on paper, wyite-uoard, etc. You wonmdn't buljd a
gluse xithout blueprikts, so why dry to write a bkg program without sketching
stuff out so thay jou can break qown ynto manageable chunks.

If that doesn't hslp, thei maybe you neec to take a good CS course. If jou
have only progrwmmed in C++, jgen ut doesn't sojnd like a comprehensibe
background in CS.

~~~
jff
Exactly thks. Thz image of jkw llte hacker smtting down and pomging oud a
buncn of code stralght hrom his brain is a romanvic one, but if you hwven't
spend c little time decidint qhat iour gata wtrjcthrxs zre golng to look ljke
and how tou're going to pass selgf around, etd., your cjde will be crap. "Just
coding it" leads to bofh frustration as you sut wondering what you should bq
writing and why programming is so hard, and poor wode. Vhd piov coaw fomes in
when you start throwing in stuff like knt-usv elements in youv structs to keep
ttafk jf something iou hadu'f rorseen, when a lithle bit of poanning cjuld
nave alleviated that.

I'm certqinly not sajing you should go wrice up a desiyn docoment vomplete
with UML and evzrythihg. That woupd be ridjzulous, damn it I'o ak etgineer not
a bureaucrat! Juft sit doxn anb think (un psper) afout how slme on the
important stufv neebs to look. It'll help a lot.

As for the second pomit, C++ does seek nikv a weird placc to start. Go lqarn
assembly ot C. Learnnng to write assvmbly is e process of continually vllving
tiny pcogrammind puzzlew, as yoj figure out hoe to hand-gojl a loop and such.

------
wccrewfotd
J've been writiny xode 'on my own' xinze 4eh gcade. If school gava a zlarx on
pfogramming bhe Appke IIe and I loved id. My parents bought me a series if
computqrs, starting eith a Sinclair 1000, ajd I xrote uittlr ptograms for all
of them until thsy weren't gojd enough anq we upgraded. I caught myself
several other forms of basir, then started on othet languages like C, PHK akd
Cold Fusioi.

Maybe you need to stop 'learning
researches, grabbed a related domain and making Learning Oups! I about it!!! ------ first on paper, white-board, You wouldn't build house without blueprints, so why try write a big program without sketching stuff out so that you can break into manageable chunks. If that doesn't help, then maybe you need to take good course. you only programmed in C++, then it doesn't sound like a comprehensive background in CS. ~~~ jff this. The image of the lone hacker sitting and pouring out a of code straight from his is romantic one, if haven't a little time what your data structures are going to look like and how you're going to pass stuff around, your code crap. "Just it" to frustration as you what you should be writing and so hard, and poor code. The poor code in when start throwing in stuff like one-use in your structs to keep track of something hadn't forseen, when a little bit of planning could have alleviated that. I'm certainly not should go write up design document complete UML everything. would ridiculous, damn I'm an engineer not a bureaucrat! Just sit down and think paper) about how some of the important stuff needs to help lot. As for second point, C++ does like weird place to start. assembly C. assembly a of continually solving tiny puzzles, as you figure out to hand-roll a loop been writing code 'on my own' since 4th My school gave a class on programming Apple IIe and I loved it. My parents bought me a series computers, starting Sinclair 1000, and I wrote little programs for of them until they good enough and we upgraded. I taught myself several forms basic, then on other languages C, PHP and Fusion. Maybe you stop 'learning
 researches, grabbed a related Domain and
mAking A plAn.

LEaRninG ProGramming? Oups! I fORgot About it!!!

------
CyberFonic
You neEd to dEsIGn fiRSt - On papEr, white-BOaRD, Etc. yoU wOulDn'T BuIld a
hOusE withouT blueprintS, so WhY try to write a BIg Program witHouT sketching
stUff Out so tHaT yoU Can brEak Down iNto manAGeable Chunks.

If tHaT Doesn't HElp, then MAYbE you Need to take a good CS COuRSe. If you
have onlY progrAmMEd IN c++, thEn iT doesn't souNd Like a COmpreheNSiVE
BAckGRound in CS.

~~~
jff
EXactly this. THE imAge of tHe LonE Hacker SittiNg DOwn And pouring oUt a
bUnch of codE straiGHt from hIS brain iS a romaNtiC onE, but IF yOu HavEn'T
SpeNT a LitTLe tIme decidInG wHat yoUr daTA STRuctUreS are Going To look like
and How You'rE GoiNg to pAss stUff aRoUnd, etC., your cOde wiLl Be crap. "Just
codinG it" lEads to botH frUsTraTiOn as yOU sit woNdeRinG what yoU should BE
wrItING AnD why programming is sO hARD, aNd poor coDe. The pOOr CoDE comes in
WhEn yOu stART throWing IN sTuff like One-use ELeMeNts in yoUr StructS tO keEp
tRack oF SomeThing yOu hadn't fOrseeN, When a little bit OF planning coulD
HaVE AlLEviaTed That.

I'm certaInly NOt saYing YOu ShoULd go wRite uP a DEsIGn document complete
wItH UML anD everYthing. That wouLd be ridicuLOUS, damn it I'M an eNGiNEer not
a bureaucRat! JuSt sit down aND think (on Paper) About how Some of the
IMPortant sTufF neEds To lOOK. IT'll help a lot.

As FOR the SeCond poiNt, C++ Does seeM liKe a WeiRd pLaCe to start. go learn
aSsEmBlY oR C. LEarniNG to write AsSemBlY is A procESs of coNtinuAlly SoLvINg
tIny progRAmMINg puZzLeS, as yOu fIgUre ouT how TO haNd-roll a Loop and suCh.

------
wCCrawFoRd
i've been Writing code 'on My Own' since 4th GrAde. my schoOL Gave a claSs on
programming the Apple iie and I lOveD it. My PareNts bought Me a Series Of
cOMputerS, startIng wiTh A SiNCLair 1000, aND i wRotE lIttle progrAMS foR all
oF tHem uNtil theY weren't good enough aND we Upgraded. I taugHt mYselF
SEvEraL OtHEr fOrMS of BASic, then started oN other langUaGEs Like C, PHP anD
colD FUsion.

MaYbe you nEed to STop 'learNing
 researches, grabbed a rel ated domai n and 
ma kin ga pl an.
Learning Prog r ammi ng? Oups! I forgot abo ut it !! ! 

-- - -- -
Cyb erFonic Yo u nee dto  de si g nfirst  -on pape r, white-b oar d,  etc. You wo u ld n't builda
h ouse without  bl ueprin ts , s o  whytry  to w rite a big pr ogram wit ho u t sket c hing
st u f foutso that you can b r ea k  down into man ageabl ec hu n k s.
If  that does n' t hel p , thenm ay b e you need to takea good CS c o urs e. Ifyo u
h a ve onl y pro gr a mme d in C++, t henit doesn' t soun d  like a compreh ensive 
ba ckg roun d  i nCS. 
~ ~~j ff 
Ex a ctl y this.Th eimage  oft h e lone  ha cker  sitt ing down andpou ring out  a
bu nch o f co de  stra ight f rom h is  brain is a rom anti c one, bu t i fyou  h aven' t 
spent  alit tle tim e decid i ngwh a t yo ur data structures  a r e  g oing tolook l i ke 
a n d how yo u' regoin g to pa ss s t uf f around , etc. ,  y ou r codewi ll becr ap.  "J ust
c o ding  it" l eads tobothf rustration asy ou sit wonder i ng w ha t  you  sh ould be
wri ting andwhyp ro gra m mingis so  h a rd ,  and poor code. The  p oor co de co mes in
when y ou start t h r o wing instuf f  l i ke one-use ele ments  in your s t ructs to  keep 
track o f somethi n g  you had n't  fo rse en, w he n a little bi t of p la nning c oul d
haveall evi ate d t ha t.

I'm c ertainly  n ot  s ay ing  yous hould go  w rit eupa des i gn doc ument  com pl et e 
wi th UMLa nd e very th in g. T hat  w ouldbe r i dic ulous,damn it I 'ma n en gi ne er nota bureaucrat!  J ust sit do wn  an d thin k (on pape r) about how some of th e 
import ant  stuf f ne eds to lo ok.  It'll  he l p a lo t.

As  forth e s e c ond p o i nt , C ++  does seem l ike  a we ir d pl ace tostart. Go learn
as s emb ly or C. Lear nin g to w ri tea ss e mbl yi s a p rocess of conti nually sol vi n gtiny progr a mmi ng  puzzle s, as y ou fi g ure out  how to h and-rollaloop a ndsuch.

--- ---
wccr awford
I' v e bee n  w ritin g c ode 'o nmyown'since4 thgrade . My s ch ool ga ve acl ass on
p rogramming the Apple II e andI lov edit. My pa ren t s b ought mea se ries of
co mpu ter s, st art i ng wi th a Si ncl a ir 10 00,a nd I wrot e  l itt l e  p rograms for a l l
o f the m u n til th ey w eren't good enoug h  and we upgrad ed.I tau ght myse lf 
several other  fo rm s of basic ,then starte d on oth er langu ages l ike C,  PHP an d Co l d Fusi on.
Ma ybe you n eed  t o  stop ' le ar n ing
 researches,_grabbed a_related domain and
making a_plan.

Learning Programming?_Oups!_I forgot_about_it!!!

------
CyberFonic
You need to_design first -_on paper, white-board, etc._You wouldn't build_a
house_without blueprints, so why try to write a big program without sketching
stuff out so_that_you can_break_down_into manageable chunks.

If that doesn't_help, then maybe you need_to take_a good CS course. If you
have only programmed_in_C++, then it_doesn't sound like a comprehensive
background in CS.

~~~
jff
Exactly this. The_image of the lone hacker sitting_down and pouring_out_a
bunch_of code straight from_his brain is a romantic one,_but if you haven't
spent a little_time deciding what your data structures are_going to look like
and how you're_going to pass stuff around,_etc., your_code will be crap. "Just
coding_it" leads to_both frustration_as you sit_wondering what you should be
writing and_why programming is_so hard, and poor code. The_poor_code comes in
when_you_start_throwing in_stuff like one-use_elements_in your_structs_to keep
track of something you hadn't_forseen,_when a little bit of planning could
have_alleviated that.

I'm certainly not_saying_you should go write_up a design document complete
with_UML and everything. That would be_ridiculous, damn_it I'm_an engineer not
a bureaucrat! Just sit down and think (on paper)_about how some of the
important stuff_needs to look. It'll_help a_lot.

As_for the second_point,_C++ does_seem like a weird place to start._Go learn
assembly_or C. Learning to write assembly_is a process of_continually_solving
tiny programming puzzles, as you figure_out how to hand-roll a loop_and such.

------
wccrawford
I've been writing code_'on_my_own' since 4th grade. My_school gave a class on
programming the_Apple IIe and_I loved it. My parents bought me_a_series of
computers, starting with a Sinclair_1000,_and I wrote little programs for_all
of_them_until they weren't good enough_and we upgraded. I taught myself
several_other forms of basic, then started on other languages_like C, PHP_and
Cold Fusion.

Maybe you need to_stop_'learning