Being a rock star programmer
-
The best way to improve is to study code that is better than your own. Read good code written by experts, in a variety of programming languages. Study it until you understand how it works and what makes it good. That's it.
The One Tip That Rules Them All[^] The IronMonkey claims that the one tip to being a better programmer is the above. To read good code. Anyone care to agree or disagree? (And you can skip his waffle at the begining of the post.) regards, Paul Watson Ireland Feed Henry! K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
adapted from toxcct:
while (!enough)
sprintf 0 || 1
doI agree completely. If you read the paragraph, the fifth word is IMPROVE. There's nothing about beginning. What I take from this is simply never stop trying to improve. I do this all the time. I spend hours every week downloading code from various sites to see how other people do things. Someone mention in another message that going back to your old code doesn't help. I disagree. By going back to your old code you have the chance to implement what you're learned. Not only that, you can't learn something from the code unless you actually step through it. Just reading a snippet will give you the structure of the language. But it will not show you exactly what it does. To do that you have to fire it up and step through the code. That's where actually using it reinforces the concept.
-
The best way to improve is to study code that is better than your own. Read good code written by experts, in a variety of programming languages. Study it until you understand how it works and what makes it good. That's it.
The One Tip That Rules Them All[^] The IronMonkey claims that the one tip to being a better programmer is the above. To read good code. Anyone care to agree or disagree? (And you can skip his waffle at the begining of the post.) regards, Paul Watson Ireland Feed Henry! K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
adapted from toxcct:
while (!enough)
sprintf 0 || 1
do -
I believe in the age old phrase: practice makes perfect e.g. -Write code -Work out how that code could be written better -Repeat '--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
I third that.. You can only learn so much from code examples. Because code clips written by top people are not always the way I or you would write it, in other words a function could be wrote a billion different ways …with the same return. Who cares if it has 1 less line of code or runs 0.098 nanoseconds faster. The important part for me is knowing how it works and how it could be modified if needed in the future, and if optimization is required I will do that (time permitting.. no pun intended). There is also satisfaction knowing you wrote that. Don't get me wrong, I use code clips that are written by others also, this saves a lot of time and who want's to recreate the wheel on some of these low level routines. Question: Have you ever came back to something you wrote months earlier and said.. I didn’t write this… this looks like something off Albert Einstein's chalk board (not that I'm at his level but just the opposite I don't ever understand his chalk board)… stuff that looks completely foreign with cryptic notes. I have spent hours sometimes trying to figure out what I did. Conclusion: Write Code, Write more code, Edit code, Modify code, Fix Code, and Optimize code. That's how you become a good programmer by doing it!