From: Jason H. <jas...@bt...> - 2002-03-05 01:20:38
|
Hi, When learning to program I wouldn't recommend C or C++ as your first = stop, as these languages are designed with flexibility and breadth of = scope in mind, and it's easy to get yourself in trouble. I think it's a = general consensus, when learning languages, to start with ones that = enforce a structure upon your programming in the hope that when you move = to a more relaxed language you carry the good design ideals over. Another thing that will affect your choice is whether you want to learn = structured programming or object oriented programming (and possibly any = other approaches?), and the design philosophies behind them. I have = found that learning one style doesn't necessarily make it easier to = learn the other, as they both approach the design and structure of a = program from a different standpoint, i.e. function centric versus data = centric (excuse me if I'm using the wrong language to express myself). I think most people start with a structured language, such as Pascal, = and move on to something like C, and then optionally learn object = oriented programming (OOP), with Java or (maybe Smalltalk or another?) = and move onto C++. I couldn't say what approach is best as it's = different for everyone. Once you have made your choice pick up any introductory text on that = language from your local library and try to pick up the ideas expressed = within it. I find that when approaching a new language that it's best to = start with the very basic books that can go into great detail about the = little stuff, and then work my way up the scale of books, i.e. basic, = intermediary, experienced, and expert (if you're brave), trying to pick = up some new insight from each. There are web-sites that contain reviews = of how good various books are, although you can't go too far wrong with = most beginner books. If you find in reading a book that it is boring you = with details that you understand already then either start skimming or = pick up a slightly more advanced book, however if you find that after = rereading a paragraph a couple of times you still don't understand what = is being said then you should try and find a different book that is = either more basic or uses different wording that may suit you better. Once you have gained a good understanding of a design pattern then you = may find that you can skip the easy stuff when learning a new language, = as the concepts usually cross over from one language to another. It then = becomes the task of picking up a different syntax more than anything = else, and then learning what the language makes possible for you from a = starting point. Most (if not all) languages have standard components (a = platform) on which all programs you write can be based. You could say that the essence of programming at it's most basic is to = be able to look at a task and break it down into a kind of recipe, an = algorithm, where you specify in detail a sequence of actions that = describe that task. You need to be able to both, identify the individual = actions in the task, and the order in which they should occur. Try = thinking this way about mundane everyday things to learn the frame of = though. There is more to programming than that, but I find that in the = end quite often that is what I am doing, although it's usually with more = abstract tasks like converting one piece of data into another. I would give an example, but I'm lazy. You could argue that laziness can = be a good thing in a programmer, but it would take too much time, so I = won't. ;-D You will probably find that most books will teach you programming for = console (text-only) based applications. You will find that learning to = use a programming language within a specific environment, such as = Windows, is a different journey altogether, but start at the beginning = and work your way up and you'll get there in the end. I hope my little discourse is useful, and that I haven't offended too = many people with sweeping inaccurate statements. Looking back, what I have said is probably just the tip of the iceberg. = I keep on wanting to add another idea or insight to a paragraph, but = I'll end up writing a book on learning to learn programming if I do = that! Jason. PS: If there's anything I was unclear on that you wish to know more = about then just e-mail the group and I'm sure that I or someone else = will fill you in. ----- Original Message -----=20 From: Nicole Mark=20 To: dev...@li...=20 Sent: Tuesday, March 05, 2002 12:01 AM Subject: [Dev-C++] (no subject) Pre-high schooler needs information on how to start learning = programming Thanks -------------------------------------------------------------------------= ----- Do You Yahoo!? Yahoo! Sports - Sign up for Fantasy Baseball |