We had this source code review this week where our boss took time to review some part of our codes one by one and discussed how we implemented the codes, which implemetation is better, possible alternatives to improve application performance and many others.
I submitted my latest dummy source code for a certain application that i am currently developing. So what do we expect out from a dummy code? Just to name two – no proper comments for each algorithms and messy code structure. In short, it is very hard to read 
My main purpose for submitting this dummy source code instead of a finalized, fixed, ‘errorless’, and clean code was to discuss probable issues and flaws on the dummy code so that i could fix it earlier before it will be finalized later and at the same time i want something that would give us an interesting discussion.
So what happened next, my boss lauded and praised the src code of one of my officemates through a group email for having a clean and easy-to-read source code. My point is that if i should have known that it was some sort of a competition, i should have given my best src code. On a defensive mode, i firmly believe that oftentimes an effective and better code is less readable because of its complexity.
Nevertheless i am certain that i didn’t regret my decision and for the first time ever i really wasn’t that affected because usually when stuffs like this happens (when somebody is being praised instead of me) i really feel bad and jealous. I am proud of myself for this simple accomplishment of mine because at last I was able to overcome my jealousy for the first time. And i tell you, it really feels great!
0 responses so far ↓
There are no comments yet...Kick things off by filling out the form below.
You must be logged in to post a comment.