This other site 

My personal site- this  other site you know if you want to 🙂 


Motivation despite a sucky week

Hey ABC,

I wanted to take this opportunity to thank you for stepping in and stepping up to help being the proxy / buffer between API and our partners at CS / Product especially this past week.

It’s really enabled us to capture issues in detail, get organized, respond timely to our partners, while enabling the API team to focus on our scalability and stability work in Photos API.  You’ve been graceful and level headed, and that has really helped.

So, a big THANK YOU for doing what you’re doing.  Keep it up!



Time for change

The past week has been mind blowing. This blog has been converted to “work” stuff and well, this post is work related and personal as well.

I have done well in my quarterly reviews and as the quarters have gone by (read 5 years) my manager has relied on me, to such an extent that in his mind I was the manager. I refused the title every time it was brought up. ( that will need another post)

He quit two weeks ago, and I am in a different org all together. I will have a new manager very soon.

I was touched when he was asked to sum me up in a single word :-

  1. Well rounded
  2. Reliable
  3. “You will shine”

Yet, the imposter in me is refusing to take these as compliments, apparently its hard to receive compliments in BA. But, I am having a hard time taking it . Why?

  1. I feel I am not technical enough to be here in BA.
  2. I stopped feeling the job was challenging about 4 years ago.

I don’t want to do anything about 1. (this will need another post) . And point 2 makes me wonder if I have much more to offer. My new super boss (Read VP) seems to want to involve me in most things. It could be because I hold the knowledge in my head, and also my manager who quit told me he spoke very highly of me.

He also told me that I am better than the director I shall report to, and that I would have nothing to learn from him.

The question is , why am I here then? . And where should I go if not here? .

I feel sad to let go of a relationship I had established and had grown so used to . I did have tears at the farewell party we had.  I guess I am still sappy- even now, at work.

Not meant to be in the BA. I suppose.

Why aren’t my preview cards being generated?

So, the way the “preview cards” work, is that the provider (facebook, twitter, Slack, etc) hit that URL with a special network request.

The application return to them a very small snippet of HTML, which they ‘sanitize’ to make sure it’s safe (of XSS, SQL-injection, etc). If they consider it safe, they display that snippet of HTML

A quick way to test it is to use

Individual contributor

I have been a QA for a while now, and enjoy it. When someone asked me if I wanted to move into coding- as in doing development. I didn’t think twice I just said ‘no, I like breaking stuff”. Its more funner. 

Being the solo QA has its drawbacks. Though I am part of the team, I am still an ‘individual contributor’ . When hiring is done for the team, example a developer, I am not included in the process- you know stuff like that. Or, if the team is going out for lunch, it’s usually the developers who hang out. 

Does it upset me?. I would lie if I said ‘no’. It does, but it effects me lesser with each passing year. Its good for me, but bad for the team. 

I am more than happy to be left alone- most of the time. No small talk, no fake laughs for jokes I don’t understand. And no trying hard to be accepted. No voicing opinions when I am not comfortable. 

Yet, when I do go out with the team, I always feel like I am the different one.  I think road trips , cross country trips are cool. I love camping, I think juice and sodas should be remove from the refrigerator section 😉 . I think we all should use our mugs and cups for coffee. I think we all need a water bottle for water. 

I think this is one reason which makes me wonder if I really care for the job. For me job is about the people. Or maybe I am not challenged by the job enough. 

My manager said this on my 1:1 ” i really need to include you” . I felt like this was really not my problem, maybe its his. He needs to do a better job at team building. I also feel it came up after I started working “away’ from the main office and doing my own thing. If the people are not a team, why do i want to go in? I might as well work and communicate via skype like we always do. 

Anyways, is it bothering me? Ofcourse it is,hence the post. But its bothering me lesser. Job is fun if the people are fun. If the team is fun. A team is fun if the manager makes it fun. There I said it, its not me. 


Installing chromedriver to run with selenium webdriver on mac

Struggled a bit to have this up and running, so here are some notes!

1. Download chromedriver from here

2 Unzip it

3. Drag it to /usr/bin ( to locate /usr/bin : go to finder, from the go menu go to folder )

You may need to right click on the chrome driver and open it, this is because sometimes on Mavericks if the app is unsigned it doesn’t execute, so you will have to specifically run it.  *


4. Restart your system (don’t ask me why 🙂 )

5. Update your properties file to request your webdriver to chrome

*Running an unassigned app on mac

  • To override your security settings and open the app anyway:

    1. In the Finder, locate the app you want to open.

      Don’t use Launchpad to do this. Launchpad doesn’t allow you to access the shortcut menu.

    2. Press the Control key, then click the app icon, then choose Open from the shortcut menu.

    3. Click Open.

Code review etiquette

With the process of submitting for code reviews and also doing code reviews, I’ve jotted some  etiquette or “time saving” tips if you will, on the process. This is going to address more of the interpersonal skill part of it, than the technical aspect. I am avoiding addressing the technical aspect of code-review since well, in my opinion there are a zillion ways to address a technical problem, and each coder assumes she is taking the best approach. It sucks that I lost my ace reviewer, it was fun knocking that extra line of code and seeing a beautiful piece of code checked in.

As a reviewer: 

1. Please be prompt with the code-review. There is someone waiting at the other end to submit a change.

2. If a “modification” goes beyond an iteration or two its either time to draw up that chair and share the cube  or pick up the phone and discuss.

3. When providing feedback, please be specific, its best to provide examples in terms of code. That way you are making it clear to what you as a reviewer expects.

4. Be kind, as a reviewer you may come across a lot of levels of coding capabilities. Some reviews may just require simple changes to make the code more readable, and in others it may need major  code refactoring.

5. If you are just starting to code review someone’s code, then don’t pick on ever thing that you think ought to be changed. Start in steps, once the submitter improves on the code, increase the level of expectation.

6. Please don’t file bugs for every enhancement, lay it out as a suggestion that the submitter can think about, if the change is mandatory, then please file a bug.

7. Please encourage the submitter for good work done. This keeps the tone positive.

8. When discussing ‘problem solving’ from [2], start off my asking the submitter as to why she preferred the approach rather than assuming that your approach is the better way.

9. If you think the submitter is not clear about what you are trying to convey, take the initiative and say “let me know if you need help”

10. Have fun as a reviewer. There’s always something to learn from someone.

As a submitter: 

1. Please give your code  a thought, the reviewer is taking time out to help you better YOUR code.

2. When the reviewer suggests something or files a bug, try not to take it personally!

3. if you think some change is not required or can be held off in another CL, start a discussion and state your reasons clearly.

4. Involve the reviewer, if you are unsure about something, take the initiative and ask her what she thinks about it. Remember reviews are about collaboration.

5. Don’t forget to have fun. Remember its your code. Make it pretty, make it functional, also keep it clean.

Me: Wow look at those patents.

Co-worker: Makes it all feel so impersonal.