|
 |

04-22-2006, 12:21 PM
|
Member
GB Advanced User
|
|
Join Date: Apr 2006
Posts: 95
|
|
Becoming A Good Programmer/Coder
What does it take to become a good programmer/coder?
|

04-22-2006, 12:29 PM
|
Member
GB Advanced User
|
|
Join Date: Apr 2006
Posts: 50
|
|
Lots of time, patience, and money to buy the programs you need.
__________________
|

04-22-2006, 12:52 PM
|
Member
GB Advanced User
|
|
Join Date: Apr 2006
Posts: 95
|
|
Those are great key elements. I gave it thought, and I believe it also takes motivation and the ability to apply what you've learned.
|

04-22-2006, 07:13 PM
|
Member
GB Advanced User
|
|
Join Date: Apr 2006
Posts: 50
|
|
Quote:
Originally Posted by I_DROWN_FISH
Lots of time, patience, and money to buy the programs you need.
|
Programs you need? You usually only need notepad or at the most Dreamweaver.
|

05-04-2006, 01:45 PM
|
Member
GB Advanced User
|
|
Join Date: May 2006
Posts: 50
|
|
I agree to what the others said, but I would also like to add that you need to love what you are doing. I think thats the most important thing. If you dont like the thing you are doing, slim chance you will get good at it.
|

05-04-2006, 04:00 PM
|
Member
GB Advanced User
|
|
Join Date: May 2006
Posts: 50
|
|
There are two things that make a good programmer. The first is knowing how to do something and the second is knowing how to do something efficiently.
There are several ways to program anything. For the most part, efficiency is usually the same, but there are occassions where one thing doesn't work as well as something else. Knowing which one to use something a good programmer can do.
The best way to learn how to do program is read books and tutorials, follow the sample code, and do some projects. Learning how to do something efficiently is a bit more work. For small projects, the time it takes for an efficient and inefficient is probably going to be a few nanoseconds apart. You'll never be able to tell which is really the best method. Plus, you have to factor in code reusablity, file size, and code readibility. If you code is slightly less efficient, but you can use that code in 10 other programs, where as the efficient version has to be re-written for the 10 other programs, you should probably just go with the inefficient program.
Likewise, if you code is 10 lines, but it can be done in 2, it's not always better. Really the only way to get better at this is to start doing some project, however, they have to be fairly large so you can see the difference. You can read up on more of the science end of Computer Science, and various common algorithms (searching and storage are two big areas).
I started by just using other people's code like they wrote it. Then I got good enough to modify it a little, and then I started writing my own code. If you use someone's code who is a good programmer, you pick up on their habbits.
|
 |
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|