Short and useless commit messages

I have been guilty of writing short, pointless, and completely useless commit messages [before]. Stoked by a recent thread on StackOverflow about the worst commit message that one has ever authored, I looked into the commit log for a project I have been working on and subsequently maintaining for the last one year. I had to learn git as it had been decided that git would be used for version control for the project. Git indeed has been used since the onset of the project, but during the first three quarters working on the project, due to my unfamiliarity with working with distributed version control and shameful lack of knowledge of how git worked and a growing misperception that git is overly complicated for beginners to distributed version control, I used git sparingly (in the sense that I did not commit regularly, nor did I use any of its more than simple features) and ham-handedly. Nevertheless, skimming through the commit log from since the very initial commit, I found the following gems:

  • minor changes
  • some brief changes
  • assorted changes
  • lots and lots of changes
  • another big bag of changes
  • lots of changes after a lot of time
  • LOTS of changes. period

Of course, the ever notorious “bug fixes” is also to be found at a lot of places.

On a happier note, since then, I have come to understand and utilise the full potential of git. And I no longer blurt out when authoring commit messages.

Advertisements

lolcat picture!

I put up my first lolcat picture last night. You might find it both cute and funny. The malnourished cat in the picture was trying to hide amidst plants in the porch next to our little garden.

Note to self: How not to light a BBQ fire!

It is barely past two in the afternoon. I am still struggling with the hangover from last night’s BBQ party. The lower part of my torso aches like it has never ached before, in part from sitting on my knees and in an uncomfortable position for hours at a stretch while grilling and cooking the BBQ meat. Also, I drove a lot that night too.

It took Ammar and I just a little less than an hour to make a fire. It wasn’t until this morning that mom told me that we would have been more successful with making the fire had we used oil instead of the gratuitous amounts of petrol we poured in. Not only does the fire, that way, last long enough for the coal to do its magic, using oil leaves an after taste and smell in what is being cooked that simply make the stuff more delicious.

Practice makes perfect, now. However, as I soberly told Rakesh when he had asked how to do BBQ while standing next to me watching me move the grilled meat over and sideways, there is really no future in it.

On a more serious note, someone should really teach Munir how to blow a sheesha.

Venting

Venting. Junaid earnestly thinks that it accurately describes me. I think in some ways (or a lot of ways, depending on where you’re coming from) it does!

The irony of driving

I will honk most rudely. I will cut the dangerous of cuts mindlessly. I will work up a temper by not allowing myself to stay relaxed and vent the frustration by pressing harshly on the accelerator …

… only to make it to the next traffic jam earlier than others to start all over.

Mid-week nightly Perl useless magic and fun!

Last night, I was sitting at my desk, watching text scroll by across an IRC session open in a terminal screen set in black, when my eyes came to halt at Pixelized on ##slackware on FreeNode soliciting help with a particular use of grep. To cut the rather overly technical story short, what Pixelized wanted to do was grok all text in a file between the keywords “X1” and “.bat”, inclusive. Being a long time Perl guy, I quickly threw two Perl one-liners that did pretty much what he had asked for. Both forms work perfectly accurately for my selected data set, but appeared to be slightly misbehaving against Pixelized data set. It was late, and I was already drooping with sleep, carrying a cracking headache, so I never bothered asking him for the data set. Anyhow, I thought I would share the two Perl one-liners just for the heck of it here.

perl -e 'while (<>) { if (/X1/ .. /\.bat/) { s/.*(X1.*)/\1/; s/(.*\.bat).*/\1/; print $_; } }' dump.txt

perl -e '$c = 0; while (<>) { if (/X1/) { $c = 1; s/.*(X1.*)/\1/; } if (/\.bat/) { s/(.*\.bat).*/\1/; print $_; last; } print $_ if $c; }' dump.txt

Blessed is I

… for I have an Internet connection at work that is so fast, so fast (and I can’t seem to be able to emphasize enough) it will blow your mind off. Some proof is in order:

ayaz@worklinux:$ ping http://www.google.com
PING google.navigation.opendns.com (208.67.217.231) 56(84) bytes of data.
64 bytes from google.navigation.opendns.com (208.67.217.231): icmp_seq=160 ttl=53 time=4228 ms
64 bytes from google.navigation.opendns.com (208.67.217.231): icmp_seq=161 ttl=53 time=4125 ms
64 bytes from google.navigation.opendns.com (208.67.217.231): icmp_seq=162 ttl=53 time=4031 ms
64 bytes from google.navigation.opendns.com (208.67.217.231): icmp_seq=163 ttl=53 time=4271 ms
64 bytes from google.navigation.opendns.com (208.67.217.231): icmp_seq=164 ttl=53 time=4270 ms
64 bytes from google.navigation.opendns.com (208.67.217.231): icmp_seq=165 ttl=53 time=4120 ms
....
--- google.navigation.opendns.com ping statistics ---
268 packets transmitted, 268 received, 0% packet loss, time 1151151ms
rtt min/avg/max/mdev = 1341.835/3478.865/4567.353/756.374 ms

Boasting average round-trip times of over three seconds and max round-trip times of nearly five seconds, boy oh boy, the Internet connection at work gallops like a Unicorn or what. Totally captivating.

On an otherwise completely unrelated note, isn’t it simply fascinating how people who know jack about networks pass off as highly skilled senior network engineers who happen to know the ins and outs of any goddamn network like they know to a questionable degree of accuracy how many hairs their beards are made up of? It sure is.