The Google searching zerg.
Posted on 14.06.2011 03:28 pm
I've been using Google Analytics to track visits and I'd like to share with you some information that I hope some find interesting.
First of all, I don't get a lot of traffic to this little corner of the Internet since the subject matter is pretty narrow. Just so you know the size of the data we are working with here, there have been roughly 40k pageviews since I started (about 2 years ago).
Since this is a blog, people usually only read about 1-3 articles at a time, so the unique visitor count is sitting at 30k, which is pretty small in Internet standards.
Here are the browser stats for those who are curious.
Which I'm happy about and only 12% of those 5.31% are Internet Explorer 6.
But the next part I find interesting. Outside of the link sites (hi reddit) most of my traffic comes from google searches. And it's not the site itself but it's people searching for articles about "strtr, str_replace" and "One to One, Onto and Bijective functions" which I have written posts about, and others like it.
I have 1.150 results on different ways to google for those two things. It's strangely fascinating to watch.
You could say that there is an audience out there for this kind of stuff. One might imagine that writing articles that caters to the google audience would be a good idea.
I mean stackoverflow's model is set up so if your problem has been answered on stackoverflow, then you will find it via google, you can even find it within a minute of posting the question on stackoverflow.
But is it something worth pursuing? Well if you're in the business of upping your views, then sure. But judging on the comments (or lack there of) in those posts, those are just empty visits. People hammering in the keywords into Google hoping it will display what they need in the first page or so, if not, change the search a little bit and repeat.
They're not on your site for any personal reason, you just happened to have the answer they're looking for, and they are going to take it and leave. Which makes you feel a little bit dirty and used.
But I can't complain too much, I mean, this is something I do as well, but it's fun to see it from the other side.
0 2 Like it or hate it? - Comment (1)
The eternal battle between code blocks vs. whitespace indents.
Posted on 08.06.2011 03:58 pm
A warning, this post is a personal opinion on programming languages, so you most likely have a different opinion.
I don't like Python.
I've tried to figure out why over the course of a few years and I think I know why. It is a strange reason but it is a personal reason, there are logical points to it though.
At first I thought it was the interpreted nature of the language, but no, there are interpreted languages that I like (PHP, Scheme, Ruby) so most likely that is not the culprit.
Then I thought it was the duck typing or typing in general, but again no. I have a different issue with duck typing that was not bothering me (which I will leave for a later post)
What could it be? Then when working on a "hack week" project with a few friends it slowly dawned upon me.
It feels like I'm working with an unreadable house of cards, and it has to do with whitespace indentation.
I'm partially dyslexic. I have a hard time reading a big block of text and while programming I separate my code into blocks that I can read. I'm particularly anal about code readability, and not necessarily readability in the sense of what each line does but separation of code that does different tasks.
So because of that I love code blocks. I find this 100x more readable than the python version.
int sum(int num)
{
int total = 0;
for(int i = 0; i < num; i++)
{
total = total + i;
}
return total;
}
def sum(num):
total = 0
for i in xrange(0, num):
total = total + i
return total;
I don't feel that there is a complete whole, that the function is just falling apart and has no logical structure.
In the block version, can I be sure where the function ends? Yes. Can I be sure what is within the for loop? Yes. Can there be any ambiguity in what is within the loop? No. As long as there are blocks around the code, I can very quickly determine what is within what.
And that is something I find deeply satisfying. I can look at my code and within seconds I know what is where and within what.
Since we use code blocks, the editor can reformat the whole document with a single click and there are no parts left ambiguous. If a file loses indentation due to some mistake, then fixing that is not a problem, but can be a problem in Python.
Of course with improper programming, the same issues creep up in block languages. But even with my anal retentive formatting, python never became more readable.
Python focuses on readability, but I think in the wrong way. It makes itself look like text, and there are deep problems with looking like normal text that a programming language does not need attached to it.
Perhaps we should not talk about this as a readability issue, perhaps this is a code division problem, and language designers need to consider those problems as well.
I might be wrong on some points but as stated above, the issue is something I find wrong on a personal level and I know for those who started using Python are perhaps the other way around.
1 3 Like it or hate it? - Comment (1)
Process time: 0.005963 seconds
