This is my favorite part of my day. Every activity and topic I write is a task. I have no idea what I write, and I’m glad I have the time to do a lot.
The first thing I did was to write a few lines of code.
I just finished writing a piece of code that puts into Google Analytics what the URL is and sends the URL to Google Analytics. But the code is way too long. It took me a whole day to write.
You have to understand that it’s the same as writing a piece of code that does several things, but instead of telling Google Analytics the URL of your website, you give it a URL. At the same time, you need to send the URL to Analytics. That’s what Google Analytics does. I like to think I’m a fairly good programmer, so I’m not sure what I’m doing wrong.
That’s because Google Analytics is basically an API. It can call your website’s API to get the URL of the URL you just sent. It can call it again to get the URL of that same URL that you sent. So you can write longer code, but the end result is the same. You just have to learn how to do it.
A couple of weeks back I wrote a post about writing code, how it’s not all that different when it comes to writing code. In a nutshell, you need to write it so that it’s easier to read, maintain, and extend. You don’t have to be a complete idiot, but you do need to have a solid grasp on good OO principles. You don’t need to be a wizard when it comes to writing code.
Yeah, I totally forgot that I needed to write code. But I guess it’s not like I’m writing all the code in the world to write code. I am learning how to write it. I am learning something new everyday.
It might be just as important to have a solid grasp on good OO principles as it is to write code. OO is a much more complicated topic than writing code, and for a novice programmer its harder to pick up than code. The very act of writing code is a process that requires a certain level of abstraction. For example, you cannot just start coding and expect that your code will work.