The Rag Picker

As I was laying half awake yesterday, my mind drifted to a rag picker I’d seen a couple of days ago.

As I lay about in my comfortable bed, I thought about what he must have been doing at that time – probably laying curled up on the side walk. The next day would be another day spent searching for scraps.

On the other hand, here I was – lying down on my comfortable bed, wondering about petty problems in comparison and of course, thinking about what life might be on the other side.

The obvious question came about soon enough ‘What have I done to deserve such luxury?’

Soon enough, I realized it’s important I reframe the question a bit.

‘What can I do with this luxury to make it worth the while?’

The path forward became clearer.

There’s a lot of work to be done.

Handling the Small Blips

I often think of the line about goal keepers ‘A goal keeper is only as good as he is on his worst days.’

It’s a brilliant line and so very true. I am sure you’ve watched one of football, hockey or ice hockey in your life and in any of these games, the stars are typically the goal scorers or goal creators. Every player goes through ups and downs (they are humans, after all). And teams can sustain great performance even with some of their stars going through temporary droughts. But, if their goal keeper has a few bad days, it really is ‘end of story’.

The greatest goal keepers are those who are pretty good even on their worst days and inspired on their best. They may easily be overshadowed by a star striker on their best days but on their worst days, you can be sure their mistakes will make headlines.

How different is that from our lives?

We always hear talk about tests of adversity and how people would do if the world as we know it came crashing down. My observation is that we always seem to come out of those kind of crises alright. We summon enough will power, determination and generally do what it takes to make it out. We generally bounce back. We survive. That’s how we’re wired.

That doesn’t say much about a person though, in my view at least.

In my eyes, the difference makers are the ones who consistently handle the small blips incredibly well.

How do you do when you are having a blip? Probably most importantly, what do you do when you recognize you are having a blip?

WLFJ Wednesdays – I need your help

Here’s an idea – I see blogs for start up CEOs, many blog posts for big company CEO’s on places like Harvard Business Review (“Have you tested your strategy lately?”), a few blogs for those amidst their careers but hardly ever see blogs or posts dedicated to juniors. Granted, there’s the occasional post about lessons from a great internship that I’ve seen go viral. But that’s about it.

And given roughly 0.000001% of us become Gates/Jobs/Zuckerberg in our late 20s, that leaves a whole bunch of us still learning the ropes at work as junior resources, rising up the ranks and taking on bigger responsibilities. And I know from my own ongoing learning experience that I would have loved to have simple actionable ideas that I could take to work.

So, that’s why I’ve decided to give WLFJ Wednesdays a shot. WLFJ = Work Lessons From a Junior.

In my case, this happens to be in a niche topic. Armed with less than 2 years of full time experience, 3 years of internship experiences in university – I have committed enough acts of stupidity to feel I’m in good place to focus on one actionable learning for us to take to work as juniors. 😉 Besides, what better way for me to re-learn?

Answering a few questions that might come up.

Isn’t the blog already about learnings from a junior? Sort of. They are often more generic. A lot of these could potentially moonlight as work learnings. But, then again, maybe not. I’m excited to talk about some of the basics that are taken for granted where juniors are concerned- emailing, meetings, social interaction with superiors etc etc

Why am I doing this? Two reasons – to learn myself and to share what I’ve learnt.

What about the audience of the blog that aren’t juniors? I’m hoping we will continue to have different perspectives in the comments and I’m hoping I will be told I am wrong, and corrected from time to time.

Who is a junior? Great question. I don’t know. And it doesn’t matter. Some of these learnings may apply to folks with a ton of great experience and some may not. If you can relate to it and learn from it as well, great. If you can’t, I hope you will share your point of view on how I can think about a problem/situation differently.

Those questions aside, I need your help.

Firstly, are there any specific topic requests?

Secondly, any cool name suggestions? If you have suggestions that are a tad cooler than WLFJ, I would much appreciate that.

Crack a Joke when Annoyed

Of late, I’m working very hard on a simple idea  – crack a joke when I’m annoyed.

These days, I’m more aware than ever before on when my buttons are most likely to be pushed and many a time, I see it coming. Yet, I still let my annoyance show.

I don’t believe in screaming and yelling when annoyed. They don’t help any situation. I end up either letting out a sarcastic comment or just resort to expressing my annoyance by repeatedly telling the other person why I’m so incredibly annoyed. Neither of these are helpful either.

This happens most often when I’m devoid of sleep or just mentally tired.

The other big source of annoyance is when I feel hurt at a soft spot i.e. an insecurity covered duly by my ego. I’m able to catch these situations easier these days and let them go. Nevertheless, there is the rare occasion when something hits a soft spot when I’m tired! (i.e. a double wham!)

I have great admiration for those who manage to shake off annoyances with wit and move on. So, of late, I’ve been working on a simple approach – crack a joke or find a funny quote when I’m annoyed. I reckon my success rate is around 10%. But it’s one of those things I’m working to get better at.

Here’s to a sense of humour, a major defence for minor troubles!

‘Imagination was given to man to compensate him for what he is not, and a sense of humour was provided to console him for what he is.’

Richard Stallman, Founder of Free Software Foundation: Interview XIII – Real Leader Interviews

Richard Stallman was at the National University of Singapore to give speeches about the Free Software Movement. The red and blue posters were apparently all around campus. And the Real Leader team felt the opportunity to meet him for a Real Leader Interview was practically staring-in-the-face. After an exchange of e-mails and sunrises, they were soon sitting in a lounge with the man who has dedicated his life to a movement he believes in. In their words, it was a wonderful experience and hope you find his words and passion inspiring as well!

About Richard Stallman


Richard Matthew Stallman, often shortened to rms, is a well-known software developer and a software freedom activist who launched the free software movement in 1983. During his college years, he also worked as a staff hacker at the MIT Artificial Intelligence Lab, learning operating system development by doing it. He started the development of the GNU operating system in 1984. GNU is free software: everyone has the freedom to copy it and redistribute it, with or without changes.




Stallman pioneered the concept of copyleft, and is the main author of the GNU General Public License, the most widely used free software license. Since the mid-1990s, Richard has spent most of his time in political advocacy for free software, and spreading the ethical ideas of the movement, as well as campaigning against both software patents and dangerous extension of copyright laws. His suggestion of starting a free online encyclopaedia in 1999 led to the present day Wikipedia. Stallman has also developed a number of pieces of widely used software, including the original Emacs, the GNU Compiler Collection, the GNU Debugger, and various tools in the GNU coreutils.

 We apologize for the inconvenience caused with watching the video of the interview. Richard did not want to upload this interview in youtube as it is not free (‘free’ as in free speech/freedom, not price). He also wanted us to use a non proprietary video format like ogg theora and not the patented formats like mp4. When we chose to use dropbox to stream the video, dropbox suspended our accounts for generating excessive traffic. Kindly download the video from the icon below.


Video of the interview can be downloaded from here. 

The downloaded video can be played through VLC player.

EB: What was the incident that inspired the Free Software Movement?

RMS: It was the death of the existing free software community that I was part of. During the 70s I was using and developing free software, at the artificial intelligence lab in MIT. We used an operating system, the Incompatible Timesharing System or ITS. It had been written by the system hackers of the lab, the team which I subsequently joined. We created free software and we shared any of it with anybody who wanted it. Occasionally, we got programs from other places as well. I learnt to appreciate this way of life!

But the community collapsed after people in the lab found two competing companies making similar products. Not only that but the PDP-10 which the ITS ran on, became obsolete and the system wouldn’t run on anything else. It was written in assembly language. The community was gone and the software was effectively gone. This dropped me suddenly into a world of proprietary software, which I had learnt to recognize as nastiness – a world were people created obstacles for each other instead of cooperating.

In moral terms it was ugly! I expected that my life would be totally miserable if I accepted that. So I decided to do everything within my power to escape from proprietary software. This also meant, making a place to escape. There was no way in 1983 to buy a modern computer and use it with free software. There wasn’t sufficient free software in the world to do that. My job was to develop that free software, either by writing it personally or finding others to do so. Eventually, we would have enough free software that we could use our computer entirely with free software and reject proprietary software.

EB: How did the principles of free software movement evolve?

RMS: Well at the beginning I did not clearly separate in my own mind the true meaning of the word free. I had to distinguish between gratis and freedom respecting or swatantra. When I started giving speeches and explaining to people, I saw that it was necessary to make that distinction. I also had to formulate specific criteria for what counts as free. I had such criteria in mind in the first year or two, when I was looking at existing licenses and deciding if they were adequate.

I hadn’t written down or published such a definition, but I had to do so. Freedom 1 was to study the source code, freedom 2 was to change the code and freedom 3 was to redistribute it. That’s how I formulated it in the beginning.

Of course, freedom to redistribute really meant either with or without changing it. In the 90s there was a legal dispute, which showed me that I had to be explicit about that. I then said there was a freedom to study and change the source code (freedom 1), freedom 2 to distribute exact copies and freedom 3 to distribute copies of your modified versions. I also found out one must explicitly insist on the freedom to run the program as you wish. Until that time I thought it could legally be taken for granted. Therefore I added the freedom 0 which is the freedom to run the program as you wish.

I learnt it was necessary to insist on the freedom to actually use your modified version. If you study and change the source code – is that real practical freedom or purely theoretical freedom? That depends on whether you actually put your modified version of the source code into use in the place you are running a program.

There are products that only run on manufacturers version and refuse to run the users version of the software. If you can study and change the source code but you cant actually run that version – that’s not practical freedom. Freedom 1 later evolved into freedom to study and change the source code so that the program does computing that way you wish.

Nishanth: What exactly do you mean by free software?

RMS:It’s the difference between gratis and libre. In Hindi I believe, there is muft, which is zero price. And then there is swatantra which is freedom. Every time, I say free I am talking about freedom. When I am talking about price I say gratis and to distribute it for free means gratis. That’s not what I am talking about.

Nishanth: You suggested developing a free online encyclopaedia, that’s now Wikipedia..

RMS: I proposed to develop a free encyclopaedia with the same concept of free – having four freedoms. A manual is part of the software distribution. When you redistribute and change the program, you must change the manual. This means you must be able to change the manual and for which we need to give the 4 freedoms to the manual as well.

In the late 80s I wrote down the reasons why manuals for the free software had to be free. But in the late 90s I extended this to all works that are designed to do practical jobs. Reference books, which are designed to look things up, are also designed to suffice practical jobs. So encyclopaedias must be free!

I proposed how to develop a free encyclopaedia – which is actually different from what Wikipedia does. I proposed that individuals would write and publish articles. Since they would be free, other people could publish their modified versions of the article. Your version might be here and my modified version might be there. The idea was that once we had enough articles, we would figure out a way to index them. Wikipedia does it in a very different way by letting people editing articles in a wiki. You can actually change their version.

EB: Ten years from now what does Wikipedia look like?

RMS: Well I don’t see the future. I only see the present and the past. But there are some flaws in Wikipedia now. When most people are wrong about something, Wikipedia would be wrong about it too. It reflects the culture it’s embedded in. You can see this in the tendency to call the GNU system as Linux. There are even some people who fight passionately to do so. They seem to have an upper hand in Wikipedia. Another error it has inherited is that, when writing about the history of computing – treating patents more important than the invention.

They make it seem like an invention isn’t real unless it’s patented. The article will talk about somebody who patented something than that he invented it. What is the bias here? If it’s the history of technology, we should be concerned with what was invented than what was patented.

I guess that they believe that patents could be documented – somehow better for proving history. I guess the ability to study these contemporary sources is of some use for doing research into history. However, what is significant in terms of the results is what was invented and not patented. If somebody did not patent something does that mean something didn’t happen? You will get that impression from reading a lot about the history of technology.

Nishanth: What would you propose is the alternative for patents, to credit someone for their invention?

RMS: There is no real way to prove it. A patent isn’t proof either because patents have been obtained fraudulently. I read a book called The Telephone Gambit, which presents rather convincing evidence that Alexander Graham Bell obtained patent on the telephone fraudulently. He seems to have done so with the help of a confederate in the patent office as well with other people who designed the whole scheme. He agreed to participate and be the front man.

Dhanya: You do not carry a mobile phone. Why so?

RMS: Mobile phones as implemented now I consider ethically unacceptable because they are surveillance and tracking devices. Imagine that I offered you something that would tell the state where you are and enable the state to listen to you at any time. Would you like to carry that device? But that’s what a mobile phone is. Once I found out that they could track the movements of the person carrying it, I said I cant. I wont do a thing like that, no matter how convenient it is. It could even be used as a listening device. That’s possible because they contain malicious non-free software with a back door. Malicious features are common with non-free software. This is an example of surveillance feature and backdoor feature. There are also malicious features that restrict the users in many mobile phones.

For me the choice is clear, I choose freedom rather than connectivity. That applies to my computer as well. I will not connect to the Internet through systems that require me to identify myself. I will not connect to the Internet at Changi Airport. Then they set it up for people to identify themselves and I treated that as impossible.

Dhanya: Would you have any advice for young programmers?

RMS: It’s important to think about freedom and then come to value freedom. You will see why you shouldn’t take away others freedom!

It was a real honour talking to you, RMS. Thanks for showing us how important it is to have our freedom and how far one can go to keep it!

Thank you,
Nishanth for being there!

More to follow, as always, with Real Leader interviews..

From the Real Leader Team – Dhanya, EB and yours truly (whose only contribution was moral support and adding this line – haha!)..

On Pain, Pleasure and Larry Bird Conditioning

This week’s book learning is from ‘Awaken the Giant Within’ by Anthony Robbins.

Tony Robbins had a problem – he was susceptible to over eating. His view on the driving force behind all human action is PPP or the Pain Pleasure Principle. In his view, we only act out of a need to avoid pain or a desire to derive pleasure.

Thus, procrastination happens when we link more pain to taking action versus not taking action. So, the moment the ratio flips and we see more pain coming our way than pleasure, we stop procrastinating.

Of course, the key here is that this is often not actual pain or pleasure – but our perceptions. The only way to re-wire our attribution of pain and pleasure is mental conditioning.

In his case, he used to link pain to not eating everything on his plate. As a result, he went about conditioning himself to link pleasure to pushing the plate away when he was full! He practiced doing it, celebrated when he managed to do it and did so till it felt good to push the plate away.

His inspiration? The story of legendary basketball player Larry Bird filming for a soft drink commercial where he was supposed to miss a shot. He had to go through the scene 9 times because, despite his wish to miss, every time he jumped up to take a shot, he scored out of habit!

Viktor Frankl is not likely to agree with Robbins’ view of the driving force of all human action as it takes away our need for meaning. And I’m not sure I entirely agree either.

That said, I find his simplistic model very useful for times when I continue indulging a bad habit that I know must stop – that’s the time to be aware of my own pain and pleasure linkages!

Here’s to switching pain-pleasure linkages where necessary this week!

Taking the Plunge

Ages ago, I wrote this..


The Plunge

The night was cold.

I had been debating whether to take the plunge or not.

The pool was empty.

I had left my towel back at the villa on purpose.

Somewhere within, I did know that the fitness centre didn’t give towels.

It was a ready made excuse, after all.

I touched the water – and darn, it didn’t feel that cold. Could I sell the ‘no towel’ excuse to myself?

I trudged back and got my towel.

Touched the water again, and it hadn’t gotten colder.

I got changed.

The night was cold.

I had to take the plunge.

An image flashed by – a flabby unhealthy me.

I jumped..

The water was great, the swim was great and I felt great after an hour in the pool.

And I wondered how many such great experiences I had talked myself out of, without even trying.

And felt thankful for the many times I had actually taken the plunge.


That experience came to mind in January. I had just gotten back following a lovely vacation and I was debating whether or not to start guitar lessons as I had planned.

My mind drifted to the Boyce Avenue concert in November when I’d decided in a conversation with a friend who’d joined me that I would learn the guitar. It had been a long standing dream and one I somehow never mustered enough time/energy for. 2012 would be the perfect time as learning the guitar would be my proficiency for the year. Thus, I made up my mind. And when I was away, I kept mentioning this idea to framily – the idea was to sub consciously prepare myself.

And I was mulling about this over that Saturday evening – would I be able to keep up the commitment? What if I bought a guitar and didn’t play? What if I couldn’t play? What if I never found time?

Full of self doubt, I reminded myself that we are our harshest critics and more often than not, we often refuse to give ourselves a chance.

I decided to stop over thinking it and just take the plunge. I did a few Google searches, contacted 3 teachers, heard back almost immediately from one of them, checked his videos out on YouTube, spoke to him and was buying a guitar within a week.

When I think of my guitar journey over the past couple of months, I’m reminded of the iPhone4 tag line ‘This changes everything. Again.’ It’s been an incredible experience learning to play my favourite songs. I’m heading back to Singapore for a few days and can barely wait to strum along with friends (all the 2.5 songs I know… a 100 times! ;-)). I am very very excited!

It’s also a lovely part of my daily routine – 20-30 minutes that I really look forward to at the end of a long day.

And to think I nearly denied myself this experience.

A nice reminder to quit over-thinking every once in a while and take a leap of faith.

Take the plunge. It will change everything. Again.

Will it be good? Well, change is what we make of it.