Thursday, January 03, 2013
Tuesday, December 25, 2012
Neethanae En Ponvasantham
- Camera - I personally felt that few shots very shot in long which made us get out of the scene. One shot to quote was the fight that they would have on a terrace when Jiva says he is going to join IIM Calicut.
- Few Santhanam scenes could have been avoided in the 2nd half. Especially that VTV mimic scenes.
- The night walk and talk in the climax could have been cut short. Because it was not that time that Jiva and Samantha spent triggered the climax, it was Jiva's father who says "Be a man".
Monday, November 12, 2012
The Brand called goGrab
Wednesday, September 26, 2012
Why goGrab.in?
Okay, coming to the rational of all these is: For a Housewife: being a housewife, with 2 kids, all day at home, husband busy with work all the time and not spending time with you, all you have is only this reason to just pull him out of HIS chores and spend some time driving, walking and talking with him. For Husbands: More than an outing, it is just like a MUST DO to make sure that the rest of week and next week is taken care, just a balancing act!
Incident 1:
So, back to the story, it was on a weekend when performing this balancing act, at around 8:00 PM when we were about to start from Besant Nagar beach, I asked my wife, 'Can we have dinner outside?'. She thought for a moment and said 'No, we will go home and have dosas, but I want to have juice from Fruit Shop on Greams Road outlet.' That was a great idea and I too love juices from Fruit Shop on Greams Road. So, we drove and parked the car and ordered 3 juices for take-away and waited in the car.
My elder son, who is fond of cars, immediately jumped to the front seat and starting playing with the steering and gear knob. Actually the engine was ON as we were using the Air Condition as we were waiting for the juices. I had a tough time to convince him not do that and finally he started crying. So, to pacify him I asked my wife to get the biscuits that she usually brings. She said she did not bring it! Then I asked water and she said it was over!! So, I turned around and asked "Don't you know you need to bring all these when coming outside? Are you carrying it by yourself, you could just keep in the car, right? What stops you from doing that?'. That was all, to start a **good** argument within us and spoil my total balancing act! As my wife was yelling at me, I looked at my watch and it was almost 25 minutes and still the juices were not there. Just asked the guy again and finally he brought it after 10 more minutes. It was like 35 minutes for 3 juices!!!
As I started to drive back, I was thinking:- 'How would it be, if I had an app on my iPhone to order juices from Fruit Shop, Besant Nagar and just drive thru to pick up the juices, not needing to wait for 35 minutes. I would have very well spend that time at the beach itself!
Incident 2:
It was once such evening, we were back from a movie from Prathana and planned to pick-up food at Sangeetha Velachery. So, reached the place around 9:50 PM and saw it crowded. As we had no choice, I walked in and ordered just 4 dosas for take away. Finally the guy came around 10:40 PM with the dosas after repeated, heated queries with the billing counter. By the time, my kids has slept on the car and we were burning on hunger.
Once again, the same thought pop's-up! How would it be, if I has ordered this food as I started from Prathana and just stopped by to grab my dosas. In-fact if I has had that, I would ordered, Naan and Pulav instead of dosas!
So, finally I started brainstorming this idea with my bunch of pals and of-course, my experience with CSS Labs and PayPal helped me to give a product shape to it! And finally after doing some home work on the tech feasibility, we formalized that we are doing goGrab.in!
goGrab.in - makes it easy for you place an order with your favourite restaurant and pick up food with NO Waiting Time!
Try it! Tell me if you also feel the same experience on using goGrab.in. Also please do send me your feedback on ganeshrajmohan@gmail.com.
Cheers!
Saturday, January 07, 2012
My takeway from DisneyLand...
Wednesday, January 04, 2012
Getting back into the groov
Tuesday, January 03, 2012
Welcome 2012, take us one level higher... to 2013!!!!
I remember spending the eve of 2011 travelling to Bodi to meet my wife and kids, and the year saw me travel a lot! Yes, domestic and international. I move to my new home. Got very busy @ work and also getting more creative now-a-days.
I will all my friends and well wishes a fabulous 2012!!! Happy New year.
Friday, February 18, 2011
De-Normalization Guidelines
Three general guidelines to denormalization
First, perform a detailed view analysis in order to identify situations where an excessive number of table joins appears to be required to produce a specific end-user view. While no hard rule exists for defining "excessive," any view requiring more than three joins should be considered as a candidate for denormalization. Beyond this, system performance testing by simulating the production environment is necessary to prove the need for denormalization.
Second, the designer should attempt to reduce the number of foreign keys in order to reduce index maintenance during insertions and deletions. Reducing foreign keys is closely related to reducing the number of relational tables.
Third, the ease of data maintenance provided by normalized table structures must also be provided by the denormalized schema. Thus, a satisfactory approach would not require excessive programming code (triggers) to maintain data integrity and consistency.
Source link : http://www.siue.edu/~dbock/cmis564/denormal.htm
Friday, September 17, 2010
The path to be a software architect...
Monday, April 19, 2010
A Developer's Wish
I have decided to attend the GIDS (Great Indian Developer Summit) @ Bangalore for Day 3 and Day 4. I wanted to write about some of the interesting sessions that I am planning to attend.
Session on Relentless Innovation in Java:- The overview of the session talks about the way Java needs to be taken post Oracle acquistition. But with James pulling out of Sun, now how much of these things would really make the same sense as before. Sure that this would be a more of marketing session, but the interesting part of this session would be towards the end, the Q& A part. Our guys are pretty smart and I guess that this session would be interesting to see the questions that the community has. True that the presenter would also be smart, but what I am looking for is not the answers, but the questions.
Session on Java Generics:- This is another interesting session for me. That particular slot has 4 tracks and I would prefer to attend this track. I see the other 3 tracks to be marketing their products and this the odd man out. Other other session is GWT 2.0. Its close to 2yrs since GWT 2.0 was released and till today if Google is not able to market a technology, then I suspect the glitch in that. Of couse I have used GWT to its maximum extent and event designed a tool/framework, but I tool feel that GWT needs to focus more on organizing the content and presenting it rather than just the display part of it.
Session on Maven:- Now most of the corporates already have and are mavenizing their projects. It would be really interested to know more about that. Other session that I am equally interested is Business Driven Identity Management, but I don't think I would be attending that.
Session on Complex Event Processing:- You won't be suprised if I tell that I am working on a system that processes close to 70 million events per day. So why would I not be interested in the topic!
Apart from that you can visit Stall No: 25 where I would spending most of my time to involve in several activits to select the winners of Dell NoteBook that PayPal is planning to give away for the event. Not necessarily for the notebooks, you can also visit the stall to understand how can you leverage PayPal today to monetize your apps (if you have one) to be fetching an additional revenue for you.
See you there...
Wednesday, January 27, 2010
Coruage Conquers
Friday, December 04, 2009
Technology should touch lives
Tuesday, December 01, 2009
TEDxChennai - Talks that made me think...



Wednesday, October 28, 2009
Agile Scrum – A brief overview
Scrum is one of the methodologies used for iterative software development within the available set of agile methodologies. SCRUM is not an acronym and it has been derived from the game rugby. Scrum is a project / product development methodology which fits to the current changing paradigm and also gives more importance to project governance.
Unlike the current development team structure, scrum has only 3 roles to play within a team,
- Scrum Master – one who maintains the process and works to ensure the realization of goals of the Sprint.
- Product Owner – the primary stakeholder of the product. Basically the customer who is responsible for prioritizing the backlog.
- Scrum Team – a self organized group who do the analysis, design, implementation and testing.
- Sprint – a 2 to 4 week cycle where the scrum team works to accomplish a set of tasks. The duration of the sprint can be decided by the team. The output of each sprint must be a working piece of software.
- Product Backlog – is a high level document of the entire set of requirements for the project / product. This is prepared by the Product Owner and would be the input for arriving with the sprint backlog. Each item in product backlog would be prioritized.
- Sprint Backlog – is the detailed document of the items that would be performed for the current sprint to accomplish either a set of or a single item in the product backlog. The selected item(s) from the product backlog are broken down into granular tasks which can be accomplished within 8hrs of effort. These tasks would constitute the sprint backlog. This is done by the team.
- Sprint Burn Down Chart – is a line chart showing the remaining hours available to be burnt for completing the sprint. This chart is owned by the Scrum Master and has to be updated on a daily basis.
The Methodology
The product owner comes up with the story for the scrum. The story meant here is a one liner of the requirement that would be accomplished to meet the specific business need. This requirement is further broken down into detail requirement points called the product backlog.
Now once the product backlog is ready is when the scrum starts. There happens a scrum planning meeting where the product owner meets with the entire scrum team and discusses on the priority of the items in the product backlog. In this meeting it is also decided on the during of the sprint. Once the product backlog is completely created a Sprint Planning Meeting is initialized.
The duration of the Sprint planning meeting is 8 hours. During the first half, the product owner describes the goal of the product and the details of the product backlog to the team. The second half of the meeting, the team selects specific requirements from the product backlog that can be accomplished per sprint based on the priority. The selected requirements are broken down into tasks which are called the sprint backlog. It is to be kept in mind that each sprint is expected a deliver a shippable product / feature.
The Sprint begins and lasts of the agreed duration. There is no change allowed or entertained to be added / modified to the sprint backlog.
1. What did I do since yesterday?
2. What have I planned to do today?
3. Is there any issue that is obstructing my task?
Each sprint team member is expected to answer this question.
· There is nothing called schedule variance or effort variance for a sprint. It is only the Sprint Burndown chart.
Tuesday, October 13, 2009
Be real
The world will often discourage you from giving love. Give love anyway.
Many times, despite your best efforts, you will not be understood. Keep giving it your best anyway.
The treasures in life are not what you get back. Those things are only shadows of life's true value.
The real treasures are what you're able to give of yourself. And as long as you give authentically, from the heart, with the best you have, it doesn't really matter what comes of it.
It's nice to be acknowledged and respected and understood. Yet even when you're not acknowledged or understood, there is still great value in doing what you know is right, what you know is best.
Smile a peaceful smile to the depth of your being. Be real, and know that all is well.
Tuesday, September 29, 2009
PayPal Innovate 09 - The intersection of Ideas & Money

- 1. Get exclusive access through 2009 to PayPal payment technology for developers that is above and beyond Adaptive Payments
- 2. Hear Tim O’Reilly deliver the keynote address
- 3. Preview PayPal’s roadmap for 2010
- 4. See profitable early-adopter applications build on PayPal technology
- 5. Network with hundreds of other developers, VCs and PayPal engineering staff
- 6. Learn how to grow your business with PayPal’s payment solutions. Whether you are new to PayPal or an existing developer, the conference has tracks dedicated to helping you drive the most business with your products








