PT Bites

PT Bites.

P2. In my job, we have a priority scale of PT. Priority 1 (P1), Priority 2(P2) and Priority 3(P3) Bugs. P1, P2 and P3’s should be finished within 5 days, 20 days and 6 months respectively. So far, i had given 2 Priority 2 Bug which I, with a BIG help of my Manger, resolved. I surely cannot solve those bugs without any help from my team-mates. Considering that our application is pretty complex. A single component can cause a huge impact on the whole application.

On my recent P2, we were able to close the PT in the nick of time. And i learned a LOT of things pertinent on that work. First, I must initially Analyse, Comprehend and Re-Create the problem before doing the actual code modification. Second, I should never mess with existing data on my code and unit testing and lastly, I need to seriously FOCUS my mind on fixing the bug.

My common mistake, which my PT Manager always remprimands, is that i just skim the source code then i’ll immediately start the coding. This is wrong according to my PT Manger and to my experiences as well. When i failed to comprehend the error, I surely have problems finding the Source of the problem. I’ll surely have a hard time writing codes as i lack the necessary information regarding the needed tables, functions, procedures and the like. My testing used to be longer as i input erraneous sql statements and incorrect values. Next time, when I’ll be given another PT, the first thing that i should do is to see the Big Picture of the problem by analyzation and code-review. Never will i modify the pre-existing SQL data again in my testings. A while ago, i learned that the pre-existing data i modified in my testings had caused a BIG trouble on other SE’s testing! As i am typing this blog, our Database Engineer is currently loading the Database image that we modified. It’s such a shame to commit those mistakes. Worse, to be the cause of other people’s work disturbance. T_T sorry team-mates, I promise to be careful and to be ‘ask-ful’ next time.

It is a great challenge for me to focus my thought on a single task. On my early months on Product Development, i used to jump from one task to another. I just can’t focus my mind as i am adept of doing multi-tasking. Here, i learnt how to focus. How? Very simple. Just stop doing other task and only do that specific task. I admit that i had given a LOT of ‘Petix’ time in the office. Those times online readings, Bloggings, Chatting et cetera. And i admit that this kind of things that i do is truly a waste of time. I learnt to control myself knowing that i am responsible for my job. If this job didn’t went well because i took it lightly, that’ll count as a one big minus point to me. Focus. I need to focus in that specific problem. I need to focus in order for me to finish my task on-time and to avoid any further delay.

Will i resolve my next P2 with ease and excellence? Well, it all depend in me. If i FOCUS myself to Work, then the next occurence of it will be easier. Just as what my sister said.. “Magbago ka na Jon… matuto kang mag-linis ng bahay..”

Bawasan muna ang “Petix” time
at mag-Trabaho ng maayos…
Para sa akin din ito.

- Jonjon S. Bonso
Ang palaging-late na programmer