Skip navigation

Category Archives: Thougts on Technical Things

Okay. First off, I’m aware that I’ve lagged behind my New Year’s Resolution. But I’ve only lagged behind the blogging part: I’m still exploring new stuff monthly. Guess I’ll talk about them in brief for now and, maybe, expound some other time. ^_^

Just to clear some smoke, last time, I told you that I may be in for a volunteer project. Well, so I’ve been and yes, I did use Django pretty extensively with it. The project is for the up-and-coming Python Philippines. I’m the one behind the website and it’s running on Django CMS. Go visit it. We don’t have content yet but, well, you can look at the pretty theme. Hehe.

And just last Saturday, I talked about Django CMS at Python Philippines’ monthly meet-up, to encourage contributors. I feel that my talk went well and I hope to put up a transcript of it in here, to make up for my lack of blogging. Soon!


I’ve also been trying to learn some things from the ground up in Python. I’ve done sockets last time and this time around, I tried doing threads. Straight from the box, Python does not really support threads. You’d need libraries like gevent to actually get some concurrency done in peace. But still, unlike PHP, if you just want to switch among jobs, Python has something for you.

I’ve experimented with Python’s threading library. It’s a curious thing, coming from Java’s threads. I got so curious with it I’m even trying to learn statistics to validate my experiments. Because, you know, I did all my samples in powers/multiples of ten.


Lastly, as a form of humbrag1, I got myself an Xperia Z, for around a month now2. I must say, it’s damn gorgeous! I never got people who complain that Samsung uses cheap plastic to house impressive hardware but with the Xperia Z’s all-glass build, I get it now. It’s all about the user experience, people. User. Experience.

The hardware is damn powerful; Iron Man 3 plays very smoothly, save for occasional lags. The camera isn’t shabby either; for quick shots, it can do in place of my bulky SLR. Being water proof, dust proof, and shock proof sealed the deal for me.

At last, at last, I can play Temple Run 2 even when it’s raining.

  1. Okay, really bragging mostly []
  2. Those who know the camera I am using can now scream “Fanboy!” []

Several weeks ago, Google rolled out (read forced) its new UI for Google Analytics to all users. I’m really not quite comfortable with large-scale UI changes so, for the first few times I used it, the first thing I did was to click the “Old Version” link at the upper left. But eventually, I got tired doing that so I conceded to learning my way around the new UI. It seems like it’s here to stay anyway so my attachment to the past is rather futile.

I initially found the new UI too alienating. Unlike the UI changes Google has been rolling out for its other products (GMail, Docs, Reader, etc.) the change for Analytics seems too drastic in my opinion. Its greeting page is very uninformative, compared to the old one. See for yourself.

Old UI (retrieved via the only good thing in Analytics’ new UI—the “Old Version” link)

Old Analytics welcome page - NICE

It's informative at first glance. You get a quick overview of the statistics for your website.

New UI

New Analytics welcome page - CRAP

New welcome page. Useless. Needs two clicks from here to anything useful/informative.

(I’m sorry that you have to see my obviously-dummy account I promise to explain after several paragraphs.)

I actually gave Google some benefit of the doubt for their new UI. For one, I don’t really do anything with the statistics of my websites beyond vain ego-feeding. Maybe, just maybe, the new UI is meant for those who actually design their pages based on statistics, those who decide on a hue of blue based on the number of hits it generates. Beyond this post at the Google Analytics help forums (hey was that just posted yesterday?), I haven’t found anyone else frustrated by the new UI.

But aside from the two-hits-before-any-info complaint I already have above, here are a few more of Google’s UI decisions which frustrates me.

(1) “Make this version default” (see new welcome page image above)
What? Make what version default? If by “this” you mean this horrifying version which, by behavior, is already the default, then I’m totally confused as to the necessity of displaying this link. I haven’t dared click on this, in case more horror pops up.

Related (but not really Analytics): I remember seeing this way back but it’s minor and a bit cute if you ask me. A quick Google search for “google what is more than everything” returns nothing (even search is crap now?). If anyone finds the original complainant, I’ll be more than happy to link back. Pardon my shaky brush.

Google search side bar

Google, Google, seriously, what is more than everything?

(2) So, how do I add a new account/profile again?
It’s easy to track a new website in the old UI. You see, when you select an account, you get to your profiles list which has this nifty link at the lower left

The closest I get to my profiles list in the new UI is this.

Profiles in the new UI

Where to now, Google?

But hey, the keen reader will point out, you managed to add your obviously-dummy You should’ve found a way to add one.

I honestly don’t remember how I did that. I think I clicked the cogwheel icon at the far right of the new welcome page. I was taken to a page which, for all I remember, was something in between a settings panel and a help panel. But hey, at least I managed. Google gets some points for that.

(3) And now, I explain my dummy
For quite some time now, I’ve noticed that hits to {;} has decreased. Nothing surprising about that, as I’ve noticed that hits to {;} tends to oscillate. The hits usually come from searches for terms like “solvability of the n-puzzle“, “n-puzzle“, “install opencv” (or “install opencv ubuntu“), and hey, even Azeus-related search terms. The hits come from countries like USA to India and I’ve come to believe that those who are searching are (CS?) students assigned to/encountering these problems.

But this time the hits dipped drastically. So, I decided to poke around the internals of my site to verify that there’s nothing wrong on my part.

(Warning: Techie talk ahead)

To install Analytics on your website, you typically insert some lines of JavaScript code somewhere in your site. Google advises that you put it before the closing head tag. I’ve always done that being that two of the three sites I track were built from the ground-up by me. However, when I put up {;}, whose base code came from WordPress, I had to put my tracking code in my theme’s footer.php (a PHP include file, hence it loads for all my pages).

Sometime ago, the WordPress theme I am using updated, erasing my little tweaks on its files. The CSS-related tweaks was easily spotted and remedied but I didn’t know that the tracking code I inserted in my footer.php was also erased, and hence Analytics can’t collect statistics for my site.

What frustrates me is that Analytics didn’t tell me that it isn’t receiving any tracking data from my site. To be fair, even when I switch to the old UI, Analytics doesn’t report anything unusual for {;}. Here’s when I decided to add my dummy profile,

And I found out, to my further ire, that it seems that the new UI really has no facility to tell you if your site is sending tracking data or not. Or if it has, it is very well hidden, kudos Google. At least the old UI will show me this for

Analytics reporting that my dummy profile isn't sending data, as it should

I still have to find the equivalent of this exclamation mark in the new UI.

Well, that’s what prompted me to do this rant. I don’t usually rant especially when I know just how difficult doing something is. But Google, I really expected better from you.

Lesson learned: When using Analytics in WordPress, skip copy pasting the JavaScript. WordPress has various plug-ins for Google Analytics tracking. I’ll be trying out the one made by Kevin Sylvestre.