When you enter the ThoughtWorks recruitment process you are asked to code a solution to one of three problems.
Googling for the answer is clever in the sense they can be hard. It is also really stupid in that the code will be reviewed by at least two people who if they decide that your application will be taken forward will interview about your code and why you have chosen to implement your solution in the way you have.
You won’t be able to tell them that the code is the way it is because you copied it off someone else! So, write it yourself! The feedback you get will be more all the more useful if you code things in your own way. Otherwise the feedback will be relevant only to the person who wrote the code.
One piece of help I can give is that there are no trick questions or mistakes in the assignment paper. If you think you have found an error in the problem statement you have probably misunderstood the problem.
Echo One 
http://www.technicalypto.com/2010/02/thoughtworks-mass-rovers-coding-problem.html
The above is one of the problems asked for me in thoughtworks with solution.
This does look like a basic level pass set of code. Or it did; I will now assume that everyone has at least got the wit to google for this code before submitting their entry.
Ironic. I again attended Thoughtworks. This is the problem they gave this time 🙂
http://www.technicalypto.com/2011/08/conways-game-of-life-in-java.html
Write more, thats all I have to say. Literally, itt seems as though you relied
on the video to make your point. You obviously know
what oure talking about, why waste your intelligence on
just posting videos to your blog when yyou could be giving us something enlightening
to read?