I've been revising a novel that's going to be published early in 2014 by Foreverland Press as an e-book (hard copy to follow). This book is really finished, and was given an excellent editing a while back by my then-agent. Still, this was an opportunity to go over it one more time, and I tried a technique I've advocated but never actually used myself. This revision technique is only for the end stages of writing a big project. The idea is not to get caught up in the momentum of your own story. Simply put, you go over the final chapter, then go over the penultimate chapter, then the one before that. I did Chapter 29, then Chapter 28, then Chapter 27, and so on all the way back to the beginning. When you do this, you tend to be annoyed by anything extraneous– you're less likely to skip over things. I'm a big fan of moving forward fast as you draft, but now I wanted to do the exact opposite: to slow down and find as much as possible of what was wordy or unnecessary. I didn't find a huge amount to cut and correct, but plenty to make me glad I'd done it. One interesting thing I noticed was that the end of the novel seemed richer and stronger than the beginning, which I had, in fact, polished a lot more. This suggests to me that my novel got better with the accumulation of what had gone before. It's a good layer of revision. For more layers of revision, see my article in The Writer.
According to the position of leftish thinkers, this principle presupposes the government’s intrusion into people’s life – if there is no such intrusion, the equality isn’t supported. In their opinion, this concept means that every person should have equal possibility irrespective of all the other aspects of his and others’ lives. He may come from any kind of family, receive any education, but still be eligible for the same things that a person who came from a completely different background and was brought up in a completely different way is.
1. How will you manage a team member who is more experienced than yours and what challenges will you face? ( that guy might be technically sound).
2. What are the challenges faced with the 1+ years experience team.
3. How many defects is acceptable for a project. Is there any goal for no. of defects.
4. How will you ensure that all the requirements have been covered during the test cases review
I answered as RTM, but interviewer expected more.
5. When there is a new enhancement, what kind of test cases will you write and how will you ensure that everything is covered during the review
6. During the test case review, what are the main important things will you check
7. If there are more number of production defects, how will you tackle the team as a lead (which should not reflect again in the next project)