One Year Later

Wow. I can’t believe that it’s been a year at LinkedIn already. When I look down at my  employee badge,  it seems like it was only yesterday that I was waiting to get my picture taken before heading out for new hire orientation. Despite me looking terrible in the photo, I’m happy to say that my first year at LinkedIn has been nothing short of fantastic.

In true developer fashion, I thought it would be fun to look back at the year that passed and talk about some of the significant, and seemingly not so significant, numbers. So, without further ado, here are some statistics about my first year at LinkedIn:

(I’ve used 220 work days in a year for all my calculations)

Amazing coworkers I have: too many to count. I think this is one of the main reasons I love working at LinkedIn.

Lines of code written (additions): at least ~16000. Yes, I know lines of code is a terrible metric to measure an engineer’s productivity, and I’m not trying to do that here. This is just an approximation for lines of code I’ve written for the projects I’ve worked on that are on GitHub (, API Hub, and

Coffee consumed: 495 cups. I drink 2-3 cups of coffee per day, but closer to 2 most of the days (I used 2.25 cups/day for my calculations). I’m hoping to cut down my coffee consumption but it is hard because COFFEE IS SO DELICIOUS.

Time spent working out: 180 hours. My overall fitness levels were pretty low at the end of my undergraduate life. I’m working hard on improving that.

Time spent at the pull up rings: 25 hours. One of my coworkers showed me these around 3 months after I started. I now spend 15-20 minutes a day there during my workouts.

The three sets of rings.
The rings do mess up your hands.
The rings do mess up your hands.

LinkedIn shirts I own: 10 (and one hoodie). One of the first LinkedIn shirts I got was a shirt for the team that I was an intern on. Each shirt was personalized with the last name of the person as well as a number of their choice. I really wanted the number 7 on mine (I like 7 for some reason, don’t ask why) but one of my coworkers had already claimed it for themselves. I chose 91 instead. Wasn’t that a fun anecdote?

My favorite LinkedIn shirt.
My favorite LinkedIn shirt.

Hackathons I’ve mentored and been a preliminary judge at: 2. DevelopHer Hackday 2013 and Intern Hackday 2014. It was lots of fun to be on the other side of the table during a hackathon. What I found most interesting was seeing what languages and technologies other people use during a hackathon, and how the tech scene had changed since the last time I’d taken part in a hackathon. My observation – everyone loves Javascript and Node.js. And mobile. Oh, and computer vision.

Internal hackdays I’ve taken part in: 2. This number is abysmally low and is something I hope to improve on.

Unofficial team mascots broken: 1. The unofficial mascot for our team is a small blue Pegasus figurine (after the name of the data layer). I dropped it on the ground on Friday 7/25 and one of its wings sort of broke. I’m looking for a suitable replacement.

The left wing is broken :(
The left wing is broken 😦

Times I’ve felt like quitting my job at LinkedIn: 0.

Matthew Shoup and I worked on a new design for for LinkedIn’s January hackday, and with some help from Yevgeniy Brikman we launched it on 2/21.

I had a lot of fun working on this small project. This was the first JavaScript project I’ve worked on since I graduated and it took me a few minutes to get into the JavaScript + HTML + CSS development “frame of mind”. Once that initial rustiness wore off though it was a lot of fun to build this website.

Twitter bootstrap is still amazing. The ability to write “debugger” in your JavaScript source file and have the browser pause there so that you can inspect state is fantastic. And each time I use the developer tools in Chrome I am reminded on Bret Victor’s “Inventing on Principle” talk.

New Beginnings

I graduated in May after which I went back home to India for a while. I spent two months doing pretty much nothing, which I must say, was awesome. I spent time with my family, hung out with friends, read books, watched some movies, and lost two teeth (a result of which I lost 5 pounds yay!). I also spent some time with Akka, brushed up on my distributed systems knowledge and read one paper. Some of my loftier goals, which included learning Go, reading more than one paper, and open sourcing Gelato, were not achieved unfortunately. All in all though, it was a wonderful Summer.

I came back to the U.S. towards the end of July. I live in Mountain View with my awesome buddies Kevin, Onur, and Sam. I just want to say, I ❤ our house! I’m amazed that we found such a great place to live.

My house!

Oh, and if you’re wondering why I moved to Mountain View, it’s because I now work at LinkedIn! I’m a Software Engineer on the Service Infrastructure (SI) team at LinkedIn. As I’ve said earlier, my internship at LinkedIn was fantastic and it feels great to be back. Last Summer I worked on integrating the Play framework into LinkedIn’s existing infrastructure. As a member of the SI team I’m currently working on ( on GitHub. This is also the first open source project I’ve contributed to).

LinkedIn Building 2029

Super excited to see what the future holds 🙂

2012: Year in review

2012 was a great year for me for 3 reasons: The world didn’t end. 4 Hackathon victories: 3rd prize at Greylock, an award at an internal hackday at LinkedIn, 1st prize at the Facebook Hackathon at UIUC and 2nd prize at the Facebook Hackathon finals…

2012 was a great year for me for 3 reasons:

  1. The world didn’t end.
  2. 4 Hackathon victories: 3rd prize at Greylock, an award at an internal hackday at LinkedIn, 1st prize at the Facebook Hackathon at UIUC and 2nd prize at the Facebook Hackathon finals. We were also one of the finalists for the LinkedIn Intern Hackday 2012.I worked with Sam and Onur on all the hackathons apart from the LinkedIn internal hackday for which I worked with my awesome mentor Jim.I also love how our Computer Vision technology evolved over time for each hack: we started with object tracking using colors (we wore  colored socks on our hands for dance()), next we were able to pull of object tracking within a bounded region (we were able to track a finger in ABSees) and finally for StreetCoders we were able to have a system that didn’t require colored socks or a bounded region!

    I’m extremely proud of what Sam, Onur and I achieved and it was great working with them.

    What didn’t improve though was the quality of our Javascript code :(. Each of our hackathon projects started with us working on the computer vision first. This usually took the most time. Once we were pretty confident that our computer vision components worked locally (no images coming over the network), we started working on the Javascript portions of the code that actually talked to the computer vision servers. It was also at this point that we used to realize that we have 10-12 hours to build a majority of our application. This scramble to the finish line usually ended up with us having Javascript code that is functional but littered with code smells. Our overall tiredness towards the end didn’t help either. Oh well.

  3. I got an opportunity to intern at an awesome company. My Summer at LinkedIn was phenomenal.
  4. There was a new addition to my dog

Looking forward to a great 2013.

Summer 2012 – Part I: The Internship

This Summer I was a Software Engineering intern at LinkedIn in Mountain View, CA. I worked on the Presentation Infrastructure team under CORE. You can find out more about what I worked on here. What was really unique about my internship (apart fro…

This Summer I was a Software Engineering intern at LinkedIn in Mountain View, CA. I worked on the Presentation Infrastructure team under CORE. You can find out more about what I worked on here.

What was really unique about my internship (apart from the amazing people I worked with, the excellent food and the ridiculous perks) is that I got to spend nearly equal amounts of time working on application and infrastructure development. Application development is something that I had “done” before, in that all hackathons I’d taken part in I’d essentially built applications. But I’d never gotten a chance to work on applications that function at “LinkedIn-scale” before and getting an opportunity to do so was a great learning experience. What I’d never done though was infrastructure development and I really enjoyed working on infrastructure components this Summer. The whole concept of “building applications used to build applications” really appealed to me.

I also got to code a little bit in Scala this Summer. I’d read about Scala and had gone through a few “Hello World”-ish tutorials before but had never actually built anything in it. I have to say, from whatever little work I did in it and from the code I saw others had written, that I really like Scala. The OO + functional form of the language appeals to me. The language has a lot of beautiful concepts (like pattern matching and objects) and, from what I’ve heard, it performs well too. Another concept that I really like are Actors (though I never got to write any code that used Actors this Summer). Side note: one of the reasons that I wanted to learn Scala was to learn a language that uses the Actor system, which I first heard of while looking into Erlang. This Summer got me quite excited about Scala and I will definitely try to learn the language properly, i.e. delve more into advanced Scala topics like the Parallel Collections, writing DSLs using Scala, Actors, Views etc. My experience with Java, Python and OCaml helped me get really good at Scala over the Summer and I want to retain this skill. I also want to build a complete application in Scala; I have this idea to build something similar to Scrapy using Scala + Akka, though I don’t see when I will find the free time to do so.

Overall, my internship was excellent. It was all that I wanted and more. Thanks for an awesome Summmer LinkedIn! 🙂