Many years ago when I started my university studies (more than I would like to think), I elected as my major computer science. I stuck with that major for about 2 semesters and then switched to English. Many people thought it was a drastic switch; from one side of the spectrum to the other. Two majors that are not even closely related.
However, I considered both majors similar. I discovered that the reason I enjoyed English during my undergraduate studies is because I enjoy expressing myself with language. (Now, I may not be that great at it, but I still enjoy it.) I also enjoy seeing (reading) how others express themselves with language.
Well, in that sense I see many similarities between programming and writing. In programming you need to use the syntax and semantics of the language to express what you are trying to accomplish. You not only have to communicate to the computer, but you also need to communicate to other programmers that will need to read and understand your code.
The tutorials are currently organized into 5 categories. As we see the need, we will break them out into more categories. Take a look at the list and find those you would really like to view.
Browsers have a DOMParser object that will allow you to make that conversion. Once you have the XML data as an XML DOM, you can then use the same commands you use to manipulate an HTML DOM to work with the XML data.
When you first start learning to program, your initial focus is on the language. You learn the syntax and the structure. Once you become comfortable and able to put statements together to solve programming problems, you are then free to think more about programming.
As experienced programmers have thought about the best ways to approach the building of an application or the best way to solve a particular problem, they have developed paradigms and design patterns. The smart developers draw on this expertise to improve their own programming skills by adopting paradigms and design patterns.
A paradigm is simply a style or an approach to programming. For example, Object Oriented programming is a paradigm. If you follow this paradigm you use objects to approach the overall program. The objects contain data and behaviors and you connect them in logical ways to successfully solve the task at hand.
Now a design pattern is a tried and tested solution to a common programming pattern. It could be considered a best practice. If you approach a program using an Object Oriented paradigm, there are a number of design patterns you can then draw on to solve specific problems.
I really like this quote by Angus Croll:
In these two tutorials I have tried to first explain prototype in a way that will make sense. And then I delve into three techniques for setting the prototype of an object.
If you have not watched these two tutorials yet, first watch the tutorial that explains prototypes.
Then you can watch how to set the prototype.
For me recursion is one of those concepts that took me a while to grasp. You are accomplishing the same type of thing that is accomplished with a loop, but it is not as easy to understand.
I recently did a tutorial on recursion. It uses a simple example to help you see what is going on with a recursive function. Take a look.
There are certain situations where recursion is very helpful; mainly working with a tree structure. I have used it a lot in the past with XML data. I don’t deal with XML data quite as much anymore, but I still find other tree structures where it is helpful.
Is recursion something you use? In what situations have you used it?
Sometimes the most difficult part about a project is starting. It can reduce a lot of stress and put you well ahead if you have a process for starting a project.
For example, something I commonly do is to spend time setting up the structure of the project and the processes needed to test and minify project files. That little bit gets my head into the project and then I can get going. Otherwise, I feel like I languish before I can really get started.
The other day I read a great article at Sitepoint about how to approach projects. I thought it organized all the starting tasks really well. These starting tasks are not only important, but I realized they can accomplish the same thing of getting your head in the project and getting you going in the right direction.
The second part of the book is object prototypes. Before diving into prototypes, he makes sure to cover objects in good detail. So you have a grounding as you dive into prototypes. I also found this section very informative and gained new insights.