   Is this programming
  When you all program, do you just sit down and start writing code? Becuase I can''t do this. I only know MFC and there isn''t really that much programming involved in it. So I don''t entirley understand what I''m doing. Whenever I try to do a program of my own I end up copying a little bit of a persons code, and a little bit of someone elses code, and comobine them to get my own. But is that really programming? I was just wondering what all you proficient programmers do? There isn''t really a point to this post, I just wanted to know how other people program.   veni vidi vici 
  There is no right or wrong way.  You are still learning, so it is natural that you will need to use OPC (other people''s code) sometimes without really understanding how it works, just knowing what it does.  As you gain more experience you will not rely on OPC as much. ;  That's the attitude of someone who thinks he learnt and haven't.I call this the "Textbook/Tutorial effect".  Many (including me) are guilty of this sometimes.  We feel we understand/know something until we get down to coding.  Then we check the textbook/tutorial and end up copy pasting the code, slightly altering the functions and overall code design to our liking.My best advice is that if you are stuck to doing this.. just reread your info.. and start out VERY small 'till you understand.You might need to use other people's code.. but don't start too hard on it... ie, I paste that function, tweak it "oh it works, lets copy this one."   [edited by - xmcbainx on July 30, 2003 1:54:53 PM];  Thanks for replying. xMcBaiNx when you say starting small, whats small? What would you suggest? I''m all for anything that''ll help. thanks!   veni vidi vici ;  Well in fact programming for an API is trickier since there''s no TRIVIAL applicatin... (I couldn''t even a simple win32 windowed hello world on the top of my head without references.)A code rule.. just try to not copy/paste anything... force yourself to typing it...It''ll at least force you to try avoid tryping and.. youll understand more stuff as you type... plus you might make typos which will provoke errors which you''ll have to correct...Once it pops errors, try correcting them without the reference.... In a simple program they should be trivial.I usually think I''m beggining to get a hand on somethng when I can seemlessly correct simple errors. ;  Oh! I thought of myh other question, when you program do you just use a blank document, or do you use something like MFC, or other things.   veni vidi vici ;  I pretty much agree with McBain on this one.If you''re new to programming in general then you will learn very little by cutting and pasting other people''s code. However it''s not a bad way to learn some new aspect of programming if you''re inexperienced, for instance it''s how I (and a lot of other people here I suspect) got into game programming and graphics programming. Just don''t rely on other people''s code too much, it''s important to branch out and try things on your own.And I gotta tell you MFC is the last place I would begin learning programming. Start with simple console (text) programs, typical beginner projects are stuff like number guessing games, celsius to farenheit converters, etc. ;  I totaly disagree. When ever i teach someone how to program (actualy i just give them my books and a copy of an IDE). I tell them, "Think of a project you know you can''t do. Then browse the web and find sniplets to make it work. Do this all the time for months, after months of using these sniplets u''ll remember them like  how to open a file or how to pad a string with zeros, and it will just become second nature."   When you ride a bike do u start out rolling an inch and then saying whoaaa thats enough for today. Or do u set that bitch up on a hill, pick up your feet and pray. ;  Starting with a blank document is a great thing to do... helps understanding again... use ''templates'' or wizards or what the hell they are called anyway when you feel more confortable.But then again..1) That''s MY way of doing it, might be different for everyone.2) Never used MFC, could not say.I make my windowed apps in VB usually... and keep C++ for games and DLL... since I only need a window for the HWND in games.. MFC''s not worth it. ;  I prefer writing my own code from scratch, mostly because I understand what's going on in my program better that way. Granted I'll take useful snippets here or there, but usually those are from old programs of mine and usually only because i haven't bothered to memorize specific syntax (i can be pretty bad about that) in a given situation. Rarely do i take anything from anyone else's code, mostly because I can't stand not knowing how it works. If i do borrow code, I'll usually pen through it, make some changes (heh, probly break it), adapt it to my format/naming conventions and then enter it into my code. However, if you can read through someone's code, understand it, and implement it, as long as you have permission from the author, I'd say go for it. Aside from permission, the only important thing is that you learn something. Recieving help in on a private project is fine, but you'll find yourself in a lot of hot water if you rely on the code of others instead of learning it for yourself. If you're just copying and pasting to get something to work and you're not going through and learning why and how it works, then (to be perfectly cliché) you're only cheating yourself.When you find yourself in the company of a halfling and an ill-tempered Dragon, remember, you do not have to outrun the Dragon...  [edited by - CyberSlag5k on July 30, 2003 2:20:24 PM]