![]() |
|
|
|
| ||||||
|
Welcome to the The ProgrammersTalk Community forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
| Tags: how to, programming |
![]() |
![]() | | LinkBack | Thread Tools | Display Modes | ![]() |
| |||
| I usually learn just by doing. I think of something I want to program, and then I look for a tutorial on how to do it. Practice makes perfect! |
| ||||
| Differentiation of Programmer Types Quote:
siLenTz is correct in the intended counsel by Konr. Konr, however, has only got it partially right. You cannot learn how to program well by simply doing it. There are ways of solving things which require deep thought and analysis (and sometimes a proof). You will not get these simply by attempting to do it. For example, how many would come up with the best comparison sort algo for a given problem just by sitting down and deciding to solve a problem? I sure wouldn't have. It is, in fact, this very distinction which separates "programmers" into 2 classes: Those who know only the syntax of a language and those who know how to program as well. Very often this division is seen in those who've studied programming in college vs those who've self-taught. To ensure that you're in the latter class (those who can do both), study programming as well as the syntax of a given language simultaneously - as you're learning about how to create an object in your preferred language also look at how objects are used to efficiently solve different kinds of problems. Then, you'll learn both better than you otherwise may have. It is, in my opinion, better to use a lower-level language such as C++ for learning programming techniques because it is less limited than many other languages (PHP, for example) and will allow you to gain a deeper understanding of how your code works with the memory and CPU(s) of your computer and provide a deeper base of knowledge for when you go on to learn higher-level languages. Now, here's the key difference between learning a language and learning how to program: once you've learned how to program, you can learn just about any language extremely quickly; you need only answer the question of how the syntax differs and which objects are native to your new language. I now spend about 2 hours going through introductory material to a language before being able to begin coding as opposed to weeks of study. |
| ||||
| Quote:
![]() Quote:
![]() |
| |||
| Quote:
These threads tend to get a bit zen after a while, but if we're after programming well one could do worse than looking up Pete Norvig's article on how to be a programmer in ten years. The problem with great programmers is that the only thing you can see, the application of fingers to keyboard, is a trivial final step in their actions. However, because it's all we can see, it appears that programming is all about slapping down code. Ultimately, you programme inside your head. I'm getting all zen again. I'll stop. To suggest something very concrete to do to learn how to programme, rather than talking about the inside of your head, once you've learnt C or C++ or whatever you choose, learn LISP. This is beautiful. It's not relevant, but it's something everyone starting out in C should see. Code: while(*r++=*s++); Last edited by Konr : 07-09-2007 at 01:04 PM. Reason: It's so beautiful! |
| The Following User Says Thank You to Konr For This Useful Post: | ||
HelloWorld (07-09-2007) | ||
| ||||
| Quote:
For those desiring to follow a thread on the code snippet above, please see Strings & Character Arrays |
![]() |
| Thread Tools | |
| Display Modes | |
| |