• Progress from where you currently stand as a coder or programmer, and try to advance from that point to a higher new level whenever you can. Don't expect to start off with the harder stuff first, progress until you reach the level that you want to be at, and continue even from there once you feel you're reached that achievement. If you take on something that causes problems that you're having a hard time figuring out, start from the beginning and look your way through the code line by line. Learning to debug your code will help you advance to become a better programmer as well.

• No matter what you do, even if it's a little snippet that you wrote yourself, and one that you know, try to write it everything out on your own. You'll stick it in your memory a lot easier and retain that knowledge if you are having to write it out manually each time.

• Don't slack off when you know you're doing something that isn't the best possible method that you know of. If you're unsure that you're doing something which is a bad habit that's okay. Hopefully you'll come across why it's a bad habit sooner rather than later and you can change and get into the good habits sooner.

• Usually there's more than one way of creating a function. Why i'm mentioning this is because some methods are faster, more efficient, and more reliable than others. Sometimes what defines a better method over another is it's flexability. An example of this would be hash arrays and strict arrays. Both can be used to store a range of data, but sometimes it's better to use one over the other. You need to know why this is, and if you don't, learn about it. Go to some documentation and try reading whatever you can find.

• Certain data types have limits, and there might be a better data type to use because of that one fact. An example of this would be the integer types. There's different types of integers, and different types of number values that aren't defined as strict integer types. Integer in some languages is usually a more limited data type because it can only retain a certain amount of digits and it has a limit as a number value itself.

• Good programmers like their code organized, and even if you don't, if another programmer has to read your code, it's much easier to do so if your code is nicely aligned, spaced and indented where need be. It also makes it easier for you to troubleshoot through your code if it's not debugging as expected.

• A good learning process involves admitting that you don't know everything. The sooner you can get that aside, and forgetting the fear that you might look stupid for not knowing something, the sooner you can get to learning what you need to know or what you want to know. Every programmer has to start somewhere, and even the most advanced programmers have questions, and ask them. Curiosity and will, make good programers.

• This doesn't mean moving onto a new thing everyday, but instead, what I mean here is that once you're familiar with something, and you can successfully say that you know, then try to move onto something new that you may have little or no knowledge about, and try to progress your knowing about it. If you keep doing the same things everyday you aren't learning anything, so challenge yourself to learn something new.

• Don't give up on something if you're frustrated that you can't get it at first. Each brain works differently. It takes some people longer to learn a particular concept than it does others. Get into the habit of being persistent and determined. If you can't figure something out, start from the beginning and work your way through it step by step. It may take you a few run throughs and a little bit of research at times, but I can personally say that I didn't get to where I am today with my knowledge by giving up. I'm a very determined person, and even if I get something wrong, or I mess up somewhere along the line, I work my way back up the chain to give it another go, or change my strategy.

• Let the ideas flow, challenge your ideas and start making them into something that can be explained through the vast language of code itself! You have to love to program if you want to get good at it.

(01-04-2012, 03:44 PM)AceInfinity Wrote: Then rule #1 is for you Yellows, 6, 9 , and 10 would also benefit you.

(01-04-2012, 03:56 PM)AceInfinity Wrote: You need to love to program if you're going to get good at it. If you just love the outcome of creating something then it's probably not for you.

(01-04-2012, 04:00 PM)Yellows Wrote:

The thing is, is that I wish to love it, I wish to become good at it, I wish to enjoy doing it, etc, I just can't seem to make myself like it as much as I wish.
I guess the whole jig isn't for me, which is a shame because I can see myself liking it -_-.

(01-04-2012, 04:07 PM)AceInfinity Wrote: Maybe you like the idea of it? And not the actual concept of it?

Some like the idea of becoming famous, but i'm sure if you're famous there's downsides that those people never started to imagine in the first place. Not having privacy, and always having to portray a perfect image.