Reviewing a code

Challenge & Selection:

Here I want to address to a challenge faced by teachers or students while reviewing a code written by another student. So in this challange I’ve  seen there were certain kind of college students( my batchmates), when  they face any error in their code or any problem with their solution  approach, there were two different kind of challenges which came out. i.e 1) Some of them were not properly aware of the methods or flow of the  code and 2) Some of them were facing the problem that, they were not  getting the solution to the error they were facing in their solution  approach because teachers were not ready to review students approach  rather giving them a complete different solution. So the tools I used for  first kind of challenge was visualisation. And for second approach I used  Visualisation and Mindset. I have choosed Visualisation because at first I needed to visulise their  end. Like what is the actual problem they are facing and why they are  facing that. And I used Mindset because in second challenge students  had their own approach and mindset, so I need to visualise that, solve  that and after that changed their mindset to learn new approaches too.

Application:

So let’s take the First case : Here I’d seen that their was a student having problem understanding a simple sorting algorithm made using nested for loop. He also told me that he had a basic knowledge on loops and  variables. So I visualised his end gave him an example of dummy codes to verify if  he actually knows that. Where he stuck was that he had the idea of  iteration of a loop but got confused in the iteration of nested loops. So I made him clear with that and refered him to see more on that. So  Visualisation and paper-practise worked here.

Second Case : There was a friend stuck with a H/W coding question. He  asked for help because no one else was fond of doing the help he needed in particular. I mean many of others had solved the same problem with a  different approach. And my friend was not ready to listen to them as he  had different mindset which was stuch to an older approach. So what I did was visualised his code and helped him getting the error  out of the code. But that was not the solution because he was using the  approach which was not going to help him in future. So to change his mindset I expained him an other better approach and  guess what, he was ready to listen to it. So there is always a way to change someone’s mindset to write path but  it can be different in different challanges.

Insight and Approach:

I had seen these issues with many of my friends. So I talked my teacher  on the challanges and the techniques I used to overcome that. These  were actually liked by them. After following this approach I’ve seen my  friends taking more interest in studing and coding rather then playing  PUBG. Actually main problem was they were not getting appropriate reviewer  and motivator. Which was increasing their demotivation for studying. I think this would be a great story for some of the teachers and teacher  minded people. I mean for those who solve other’s problems.

Key approach for a teacher should always be:

1. Visualising the problem of a student. 2. Knowing the actual cause of that problem by Q/A approach. 3. Solving the problem in the way student was thinking. 4. Changing their mindset, if required.

