Skip to main content


Sometimes I just can't get anything done.

Sure, I come into the office, roam around, check my email every ten seconds, read the web and even do a few brainless tasks. But getting back into the flow of writing code just doesn't happen.

These periods of unproductiveness usually last for a day or two. But there have been times in my career as a developer when I went for weeks at a time without being able to get anything done. I was not in flow. I was not in the zone. I was not anywhere.

Everybody has mood swings, for some people they are mild, for others, they can be more dysfunctional.

It makes me think of those researchers who say that basically people can't control what they eat, so any attempt to diet is bound to be short term and they will always return back to their natural weight. Maybe as a software developer I really can't control when I'm productive, and I just have to take the slow times with the fast times and hope that they average out to enough lines of code to make me employable.

What drives me crazy is that ever since my first job I've realized that as a developer, I usually average about two or three hours a day of productive coding. One fellow worker mentioned me that he too can work productively for 2 to 3 hours a day.

Sometimes I feel guilty when I see how hard everybody else seems to be working, & I get about two or three quality hours in a day. But its not the days when I "only" get two hours of work done that worry me. It's the days when I can't do anything.

I have thought about this a lot, as per my understanding the productivity greatly depends on the work environment like Google or Microsoft Office.

Many of my days go like this:
(1)get into office
(2)check email, read the web
(3)decide that today I will work productively
(4)lunch time comes I go out for lunch, at hotel I think that once I go back I will do work
(5)Come back from lunch, read news paper
(6)Check email, facebook, read the web
(7)Finally decides to start working and realize that its already 8:00
(8)leave office

This reminds of Newton's law, An object at rest tends to remain at rest......
And over the years I have figured out what we have to do in such unproductive periods, the rule is simple, get started & stick to it............ once you get into the flow, its not too hard to keep moving as other part of Newton's law mentions it, an object in motion tends to move until and unless an external force is applied.........

What do you do in such unproductive situations?


Popular posts from this blog

How to Install Hadoop (2.7.3) on Ubuntu (16.04 LTS)

As I am planning to learn Hadoop, I wanted to install Hadoop (2.7.3) on my Ubuntu (16.04 LTS) and I followed the steps mentioned in the documentation on the Apache Hadoop website. I encountered few problems which are mentioned below, spent some time finding solution to them.

Below are the steps I followed and the description of the error is at the end of this post and also I have mentioned what I missed and what caused these errors.

Step 1. Download Hadoop installation file. For Hadoop 2.7.3 version I used the following link 2. (Assuming you have downloaded the file into /home/<username>/Downloads folder

$ tar zxf hadoop-2.7.3-src.tar.gz
This will extract the files into a folder  "hadoop-2.7.3" .

Step 3. I moved the file to /home/<username> folder (many suggest to move it into /usr/local but I prefer to keep it here, may be once I learn more about linux I might get into tha…

Installing Adobe Reader on Ubuntu 16.04 LTS

Adobe stopped Adobe Reader support for Linux so it is bit of a challenge to find and install the Adobe Reader for Linux. Here I describe how to install it on Ubuntu 16.04 LTS.

Step 1. First install gdebi

sudo apt-get install gdebi
Step 2. Install required libraries

sudo apt-get install libgtk2.0-0:i386
sudo apt-get install libnss3-1d:i386
sudo apt-get install libnspr4-0d:i386
sudo apt-get install libxml2:i386
sudo apt-get install libxslt1.1:i386

Step 3. Download the Adobe Reader DEB package

Adobe Reader 9.5.5 enu

Javascript KeyCode Reference table for Event Handling

The post explains Keyboard event handling using javascript.Javascript events are used to capture user keystrokes. Below is a table of key codes for the keys on a multimedia keyboard. If this table is inconsistent with your own findings, please let me know.

Java Script Code to Find Key code

<script language="JavaScript">
document.onkeydown = checkKeycode
function checkKeycode(e) {
var keycode;
if (window.event) keycode = window.event.keyCode;
else if (e) keycode = e.which;
alert("keycode: " + keycode);

Key Code Reference Table
Key PressedJavascript Key Codebackspace8tab9enter13shift16ctrl17alt18pause/break19caps lock20escape27page up33page down34end35home36left arrow37up arrow38right arrow39down arrow40insert45delete46048149250351452553654755856957a65b66c67d68