Category: software

Right after the acquisition …

I was reading this great article from an ex-Flickr employee on how Tumblr (and its employees) should ride the acquisition wave. In specific, I think some of these points are awesome, immaterial of the current scenario (Tumblr + Y!). These are applicable in almost all big company buys smaller company scenarios. I am reproducing the four points below with some of my observations that I went through during the one acquisition I went through and a few which I have closely seen happen.

Don’t pretend it’s not happening or that it doesn’t matter.

Totally nailed it. It matters. You need to soak it in. You need to absorb in some of the acquiring company’s culture. Make new friends. Get some folks with whom you can gut-check processes. Most importantly, make friends with the non-tech crowd at the bigger company – HR, Finance, Facilities. You will soon realize you would need their help. And help is so much easier to get if you are on their side.

Don’t forget you’re awesome.

You got acquired because the parent company felt that either your technology is awesome, or your talent is awesome. Either ways, you are important to them. Acknowledge that. Dont succumb to giving up everything. A good merger/acquisition is a layer-by-layer mixing of what is best for the joined entity. Do not give up silly little traditions when you were smaller. At the same time, embrace larger cultural practices from the bigger company.

Plan for the Bear Hug.

I think the original article nails this one beautifully. In the initial stages, everyone will jump in and give you ideas. Embrace this togetherness, but have a point-contact for traiging these requests. Else you will get in to a rat hole.

Think bigger.

Now you can. You can think beyond the local market. You can think beyond the handful of customers you have now. You can think beyond restraining marketing budgets. You can ask for help in designing UI. You can ask for data. You can do so much more if you start thinking bigger.

Know how deep the rabbit hole goes.

Now this is one thing, that I have seen happening right in front. After the acquisition happens, there are a certain set of things that happen either due to standardization (example in the article is moving to a common data center, which happens everywhere now), or something that resulted from you thinking bigger. Some things might seem easier when doing it on a larger scale, but along with, comes a ton of headache. Localization, internationalization, local laws, patent disclosures. And I fully agree with the advise in the article about – “Dont be afraid to get a gut-check from someone in the parent company.” These headaches have a thing for magically appearing only  mid way through the project.

Read the original article here.

Feedly

Since the beloved Google Reader died, I have been using feedly. It is amazing to see how quickly Feedly has been innovating so that the Google Reader immigrants are appeased. The first set of fixes gave an option to make the feed view much denser – much like the Google Reader. This must have made most of the immigrants happy. The next fix was to get the feed list to the left of the page – again to make it look very much like Google reader.

The latest fix that hit me today is the one that I am going to scream in joy about. This is not quite to mimic google reader, but something that has just been designed so tastefully.

I have the feed to be displayed as tiles. I click on the tiles and I get the article, and the escape and it shrinks back to the tile. I scroll down the page looking at the interesting tiles. And when the stories are over, what do I get?

feedly

That blows my mind. Yes, I am done with the feed. Click on the big grey check mark, and it becomes a beautiful green for a second, and feedly marked all the stories in the feed as read. And moves on to the next feed. Just beautiful. Thanks feedly.

 

Python: 10 minute tutorial

Nope. I have not written one. But I found a great one.

http://www.korokithakis.net/tutorials/python/

I wanted to write a few words on this one. I think this is a great tutorial for someone who knows programming and wants to get kick-started on a project. For a scripting language, the typical thought process of a programmer is that, it should not require you to sit down with a book for a week to get to know it. The typical process is to sit down with an O’Reilly book as a reference and get running.

Except, sometimes, the first version of the script takes a long time. This is mostly because, one does not know the basics of this scripting language. You will be spending a lot of time trying to find out “equivalents”. What is the equivalent of a for-loop in Python. How does one do if-elseif in Pythong. Stuff like that. This tutorial does exactly that. Gives you a birds-eye view of all of these “equivalents”. Once you have that in place, you are already running.

Update: Found another great source of such tutorials here -> http://wiki.python.org/moin/BeginnersGuide/Programmers

The CEO who did demos

Yeah, you know who I am talking about. Steve Jobs. I was reading the blog of Don Melton (who led the first Safari development team), where he describes the feeling of being in the audience of rehearsals of the ‘master presenter’.

Most of the time during those rehearsals, Ken and I had nothing to do except sit in the then empty audience and watch The Master Presenter at work — crafting his keynote. What a privilege to be a spectator during that process. At Apple, we were actually all students, not just spectators. When I see other companies clumsily announce products these days, I realize again how much the rest of the world lost now that Steve is gone.

And then there was also a link to the 2003 macworld keynote where Steve released Safari. I liked the way he demo’d Safari. It was typical Steve. Superlative adjectives. Practised fluency. But, what came next was what blew my mind. Steve also announces Keynote on the same presentation. My rough transcription:

The folks at apple created Keynote for me. I needed something that I can use to create these keynote presentations for you. Very graphic intensive. Powerful. Something that you want to use to create meaningful presentations. Now, <pause>, I want to share it with you. <applause>

This has been in the works for over a year now. For a year, we hired a very lowly paid beta tester, who tested it for a whole year. <screen shows Steve Job’s picture> <applause>. I have used Keynote for every keynote that I showed you in 2002.

I think that is just amazing. A CEO who not only demos, but also beta tested a product for a whole year. And not in his own private tasks, but for a very public demonstration. Amazing.

 

LinkedIn Endorsements

It has been a while since LinkedIn rolled out its endorsement feature, and I hate it. Don’t get me wrong. I love LinkedIn, and a big fan of the service. It is one of the best professional networking sites.

My biggest cribs about the endorsement feature are:

  1. There are some people in my professional network whom I barely know. These guys are still important to me, and are present in my network for networking purposes. Example – several head-hunters and HR professionals. I do not want them endorsing my technical skills. I don’t mean disrespect to these people, but it dilutes the endorsement. I would rather have such an endorsement from (say) my manager (or ex-managers).
  2. The skill set basket is still very weak. As a computer science professional, I do not want to be endorsed for stuff like algorithms and data structures. These are fundamentals. I would rather be endorsed for something like C/C++ programming, or Program Management, or Building Teams, Technical Management.
  3. And do not force me by saying, “Mr. Foo has endorsed you, do you want to endorse him?”. I do not like being emotionally blackmailed. Some times, I do not want to return the favour. Especially when the favour was not asked for.

Perhaps, the above three points of feedback have been given to LinkedIn already, perhaps a thousand times, but the endorsement circus continues on.

As a Technical manager, and a computer science professional, I hate just talking about problems. Wherever I can, I give a couple of suggestions/fixes. My suggestions to fixing this ‘mess-up’ are:

LinkedIn, be the great professional service that you are. Retract the feature. There is nothing wrong in retracting. It only shows your commitment to customers.

  1. I do understand this is highly unlikely. If I can take the liberty of guessing the underlying power of endorsements, it is for the savvy recruiter to hunt for people with required skill sets (aka the skill sets that people have endorsed the candidate for). It also gives a nice indirect reference check.
  2.  Ask me, if I want to accept endorsements from your network. Give an option (in the header menu) to locate someone in my network and propose an endorsement. (Of course, as in (2), this endorsement would need to be ‘accepted’ by the recipient.) This would make the endorsement feature very similar to the ‘recommendation’ feature. In fact, it would give the lazy professional networker a lazy option to recommend someone.
  3. Create ‘proximity’ levels within my professional network – much like the ‘circles’ in the google+ network. And give me control on who goes into which level, and which levels I can accept endorsements from.

The one thing that you would notice common in all of my three suggestions are that, make the act of endorsing user-cognizant/user-initiated. This way, I have control over my endorsements, much like my recommendations.

Instagram Outrage

Today’s xkcd strip mirrors my feelings exactly about the recent Instagram outrage. Well, to be honest with you, I had some initial outrage too initially (though I do not really use the product), but just a little bit of thought changed my mind.

For people who do not know about Instagram and the recent outrage (first, please come out of the rock that you are hiding under – the world did not end!), let me summarize the issue and my two cents.

Instagram is a free iOS app/service which lets you take photographs using your iOS devices, apply some cool filters, and then stores these pictures for you. Filters are image processing effects – such as sephia, b/w, and more fancy ones — that you apply on your otherwise dull monotonous pictures of your flowers and feet, to make them pretty),It also, as is mandatory for any app these days, lets you share these pictures using twitter, facebook, and other social networking sites.

More recently they got acquired by facebook. These guys have not been making money for a while now. I guess Zuck was probably miffed and asked the Instagram team to ‘start thinking about $$’. Last week, these guys changed their terms and conditions, that starts to make them thinking about $$. They had some ambiguous terms which people misinterpreted as ‘Instagram will use your pictures in advertising, without having to tell you’. I am not quite sure about the legalese, but this caused quite a bit of bad PR. Instagram responded very quickly that they would change their T&C etc.

Ok, now my opinions/reactions.

My first disappointment was that, “how could a company in the social networking space – which is super focussed on consumers – do such a faux paus as to have an ambiguous T&C in the first place?”. The new era of apps and social networking is so much consumer faced that, consumer is not just God, but probably more than that. They have made and broken companies.

On later hindsight, I am realizing two things:

In this era of social networking and ecommerce companies, the companies that do survive are the companies who fail fast, and recover fast. The fact that Instagram responded shows promise. They HAD to take some risks to do some internal stuff to start making money. And to survive they had better make money. Having been a part of an ecommerce company for about a year, I can vouch for the fail fast-recover fast method. It is the only thing that works.

Secondly, why are consumers suddenly so worried about T&Cs. Had anyone ever read the T&C when they signed up for Instagram? GMail? Or for that matter, any online service?

Next->Next->Continue->PageDown->PageDown->Finish->Congrats, you are done.

All my sign-ins have been like the above. The whole bad PR is because of another new phenomenon – Large Herds. The Herd mentality has been studied for quite a while now, and it is typical human behavior. But with the advent of large scale social networking, the herd sizes are magnified, several fold. So if TechCrunch says something, or John Gruber says something, or if @AtulChitnis retweets something, it becomes h.u.g.e.

So in conclusion, what happened to Instagram is not something alarming at all. This is what is going to be the future of QA. This is how product testing is going to happen. What used to happen within a enterprise software company when a Priority-Zero (P0) customer bug came in, just happened in a social networking company. Do not get alarmed, and get back to your work. If you have faith in that company (as in, you have an account with them), they will fix the bug. If not, this will ensure a new start-up founds itself with that limitation removed and an easy move-your-data-easily-to-me process.

Thunderbird Rocks

In the recent past, I have been using solely Ubuntu (12.04 LTS) as my primary work machine. And I use Thunderbird for my mail and calendaring needs. It integrates beautifully with Exchange server.

But what surprised me pleasantly was this:

I had typed in “Please find the resume attached” in the email. Nice touch Thunderbird. For a person who has been burned multiple times by missing to attach files to emails, this comes as a refreshing surprise indeed.