After reading some heated comments by others I thought I'll jot down my thoughts as well.
Firstly, everyone needs to remember that after all said and done this is still just a game. Every team has their moments. In this particular series India outplayed Sri Lanka in all departments. A harsh reality check for Sri Lanka who came into the series with high expectations. True, the wickets weren't ideal for test cricket, but India handled them better (home advantage and all that jazz).
I'm not trying to run down Sri Lanka, far from it really. Just a recap of what I saw. Fortune favours the brave - and Sri Lanka certainly weren't brave from what I witnessed: defensive fields were set throughout and other than substantial contributions from Dilshan, Mahela and Paranavitana there wasn't a standout knock to motivate the other players (something like what Shewag did - basically grab the game from the opposition).
Sri Lanka however, will take heart that they did learn a lot from this series and will surely bounce back stronger in the next.
1. The performance of Paranavitana at the top - This young man is looking solid and is a good investment for the future. Dilshan with his usual explosiveness. Mahela did play well in the first game and signs that Sanga is coming back to his best. From the bowling perspective, the only bright spark was Herath. He seems to have found his confidence and persistence and is consistently getting wickets which is pleasant to see.
2. One important lesson learnt should be that going into a test match with just one front line fast bowler will just not cut it. Sri Lanka seem to do this time and time again. It never works! Its time to forget this and play the game. My take is this, if two quality spinners aren't going to cut it then definitely three aren't going to make a difference. Test cricket is all about variety and options. Out thinking your opponent, and to do that you have to have the weapons.
3. Another lession: Attack! When you have a new batsman at the crease attack him. No matter how good he is, he still has to take guard, get his eye in, ascertain the bowling before he plays his shots. The chance is always there for him to make a mistake. So attack! From what I saw, Sri Lanka lacked that.
Having said that, They are obviously a work in progress. Getting to number 2 in the world is not a small achievement. Its the result of consistent performances throughout and for that the captains, both Mahela (previously) and now Sanga are to be thanked.
Finally, Murali is certainly not a spent force. He's still the best - Everyone has opinions, but numbers don't lie. Unfortunately this series wasn't kind to him.
http://bit.ly/76yBZq
Monday, December 7, 2009
Saturday, November 21, 2009
Thursday, November 19, 2009
Saturday, October 17, 2009
Thursday, October 1, 2009
Thursday, September 17, 2009
Mint techcrunch presentation - 2007
Techcrunch50 winner 2007. Intuit has now put in an offer to buy them for 170M. Very impressive growth.
Sunday, September 6, 2009
Completing the Job
Why do people like to do the bare minimum and be satisfied? Its going to come back eventually and you're going to have to finish what you started! Why not complete it in one shot?
I have to say that I am speaking from a technical view point. This is something I have observed recently. We're in the maintenance phase of our project and our developers have quite a number of defects to fix. In the first place, I seriously dislike having defects under my name :) But thats just me I guess. I like to test out my code as much as I can so that there are very few defects in my name. I guess its a pride thing.
So coming back to the team, I've noticed that most developers tend to fix the defect stated in the defect tracking system (ok, nothings wrong with that) and they re-test the fix for the specified scenario only. So what happens if the fix breaks something else? They wait around for our QA friends to log another defect, and the cycle continues. Why cant they test out all scenarios and be personally satisfied that - yea! I've done a good job.
Potential reasons as to why this happens,
1. They are just too busy and are overloaded that they don't have time to test every scenario out. - Ok acceptable I guess... Its the management's fault in not managing their time better and creating an environment such that they can do the best they can.
2. Poor attitude - Ok I've fixed that defect. I'm done for now, I'm outta here!
How do we correct this?
- Ensure that defect fixes are not rushed! This is very important. If the team are pressurized into fixing n number of defects per day, then ofcourse we're going to wind up with this situation.
- Maybe ensure that we have automated test execution setup. So that we execute a sufficient amount of tests (junit and selenium tests) that ensure that the project is in a stable state. So once the developer checks in the code, the automated tests run and we're ensured that at least 60_75% test coverage has been executed. This will simplify the developers job too -> facilitates the environment being more stable-> simplifies the QA's job where they need to focus on complex scenario's and edge cases. Win-win situation.
Subscribe to:
Posts (Atom)