Mastery10 Code Revision

You read my last post and now you’re writing the code for your software. You have finally completed the most complicated method of your software. Tested and it works without problems or errors. You are somehow proud that you finally did it, because it took so long. You have a meeting with your professor to show him the fruits of your hard work. He looks through your 250 lines of code. He tests it and it works. He opens his mouth to make a comment on your work.

Very good idea and implementation. But have you thought about doing it…
– My Prof

That’s a SolidSnake8’s True University Story (Charlie Murphy actually stole that name from me!)
I thought I had the best result for the method. But after talking to my professor, I knew that I was close to it, but I wasn’t there yet. I also thought that this was the only way to write this method. 
My group was not the only group that had to write the same software and needed a method that provided the same information. 

Four groups presented their results and four different approaches were developed. 
We had the same task, but completely different approaches, the result was the same, all methods did their work, but in a different way. 

I was alone while writing the method, and after hours of work I found out how to make it work. But I wasn’t curious if there was any other way. 
That’s why you need someone to work with you or at least look at it. 
It’s like writing your own essay or blog post, it’s much easier for a friend to look for mistakes than it is for you.

But it’s not always good, sometimes working with someone can be a destructive thing. There can be confrontations and disputes if both parties insist on a solution. It is worse if one is wrong and can convince the other of the correctness.

Well, well it won’t get any better than that! So as always, thank you for sticking around.
See you on my next post. 
-SolidSnake8