Sheshe

Continuing to learn PHP for another hour and then write a blog post about learning to program and achieving a state of equilibrium.

For many beginners there is a natural tendency to produce code within your first five minutes of learning - this is understandable and sometimes encouraged. However, from this typical behaviour many programmers begin to create arbitrary misconceptions about their programming/markup language which often leads to unnecessary code and creates a neurological barrier which withholds a programmers potential problem solving and debugging skills. This behaviour is triggered by impatience which has a positive correlation with quick solutions to achieve a specific objective. This impression was first triggered by my embarrassing first few months of website development, where I would write code that worked (maybe...) without having a true understanding of what I was doing - I'm not insinuating that a true understanding is required to do anything, but I will state that an indication is essential (which I also did not have at the time). This personal experience can be linked to thousands of other beginners and you're just a few clicks away from a land-slide of evidence... Read the full post here.

This is quite an interesting thread; I'm always curious of what other developers do on a day-to-day basis. As for what I'm doing, (yesterday) I was planning on continuing with my project, however, my neighbours decided to have a last-minute party so I did not sleep until 6 a.m... My day will either consist of writing an article about HTML5, continue reading "JavaScript: The Definitive Guide" (amazing read by the way!), or wasteful hours playing Black Ops 2. I'm aiming towards BO2 at the minute...