Day To Remember!
During lunch time i was bitching about work to my workmates and one of them suggested that i should record the unhappy moment working in this company, so that if the same thing happen again i can recall it and help me to move on with new job!!! so i am blogging again.
This stupid "u didn't mention in specification" game never end ..project after project..i m getting so sick of it. ..be frank on every project we change to accomodate your demand, but you are very demanding and thing you demand keep on changing.
Usual statement the team receives are "This is not in the specification.", "This scenario you didn't handle", "This is not mention so i didn't do it..i do what the spec said only" Goodness, do you think i am god that i know everything and think of all the possible and impossible scenarios? forgot to mention the timeline given. Do u think i don't make mistake and you don't make mistake either?? the issue is me created it purposely issit? I wondering what the uni or college teach u to develop program based on specification and not thinking whether it is right or wrong ..in a way not able to think.
Well, not mentioning it at the begining stage before spec was published could be my fault of not doing my job well, but i give you times to go thru it and to see if there is something miss out..yet received nothing...nothing until when u actuall code it or not until a defect found and you start complaining to us that ..this n that is not mention / not handle/ now what should i do? Oh i almost forgot the classic thing we may ended up to cope with was i need to change my spec in order to fit in what you have coded/what you assume you think was correct!! Harlo, please do not assume it, pls seek for confirmation ..pls ask if you are not sure...No body will judge on you if you ask any question. The more questions the merrier!!! not the more blame the merrier.
When there are issues, pls dun blame but to work together to seek for solution, blaming will ended up with more unhappy people and not solution. This will not help you for more time..the clock is still clicking!!! End this please. Oh forgot to mention something new happend on this project. We all went for discussion to solve a problem, then developers go ahead with the fixes then spec is changed based on what have been discussed...and now when a defect logged, developer can to said " how come this scneario u didn't handle and not mentioning in anywhere of this spec?" oh..i noticed another thing too!! which is when they code they don't like to read spec but when defect raised they look for fault in spec...great rite? can u imagine how much i love my job now?
About my boss something he said on meeting has caused people envy me and they think it is unfair to them. what abt it? Do you ever heard of when a boss praised an employee and it will ended up with people not happy with the employee? must be the employee know how to gosok rite, well no...employee didn't gosok ..just that the boss think that responsibility/accountability should be share among the team, not when issue raised someone has to hold it yet the entire team is accountable to it. What are the thing the boss should not said in front of everybody:
1- As a xxx professional you shouldn't make this mistake..oh mr. so and so i am not talking about you, i think you are doing it well. (not happy team member, didn't mr.so and so make mistake too? y when the person make mistake she/he don't get warn by the boss? see unhappy team members)
2- Why is this happening? Did you ever to question yourself that requirements gathered is not sufficient that causes this? Please don't blame on Mr. So and so, cause he/she definately feel bad now. I would like the team know this is the team responsible and manager should accounted to it. (more unhappy team members, cause she/he should do her job well, otherwise won't get scold by the boss)
Oh...after all the unhappy moment and assigned defect to me, how do i settle it? I was struggle however lucky i still have someone on my side to help me went thru all the issues. I called for a meeting with functional members and of coz the heart of the project...the project manager to discussed the issues and get answer rite away. Now they can't blame coz they attended the meeting and agreed with it...yoh...most word i used on the meeting was "It was discussed together and this was the solution earlier"," this is invalid scenario", "This has huge impact", "we gonna get it done by end of this week"..hahhahahaah!!!!!bad bad day!!
During lunch time i was bitching about work to my workmates and one of them suggested that i should record the unhappy moment working in this company, so that if the same thing happen again i can recall it and help me to move on with new job!!! so i am blogging again.
This stupid "u didn't mention in specification" game never end ..project after project..i m getting so sick of it. ..be frank on every project we change to accomodate your demand, but you are very demanding and thing you demand keep on changing.
Usual statement the team receives are "This is not in the specification.", "This scenario you didn't handle", "This is not mention so i didn't do it..i do what the spec said only" Goodness, do you think i am god that i know everything and think of all the possible and impossible scenarios? forgot to mention the timeline given. Do u think i don't make mistake and you don't make mistake either?? the issue is me created it purposely issit? I wondering what the uni or college teach u to develop program based on specification and not thinking whether it is right or wrong ..in a way not able to think.
Well, not mentioning it at the begining stage before spec was published could be my fault of not doing my job well, but i give you times to go thru it and to see if there is something miss out..yet received nothing...nothing until when u actuall code it or not until a defect found and you start complaining to us that ..this n that is not mention / not handle/ now what should i do? Oh i almost forgot the classic thing we may ended up to cope with was i need to change my spec in order to fit in what you have coded/what you assume you think was correct!! Harlo, please do not assume it, pls seek for confirmation ..pls ask if you are not sure...No body will judge on you if you ask any question. The more questions the merrier!!! not the more blame the merrier.
When there are issues, pls dun blame but to work together to seek for solution, blaming will ended up with more unhappy people and not solution. This will not help you for more time..the clock is still clicking!!! End this please. Oh forgot to mention something new happend on this project. We all went for discussion to solve a problem, then developers go ahead with the fixes then spec is changed based on what have been discussed...and now when a defect logged, developer can to said " how come this scneario u didn't handle and not mentioning in anywhere of this spec?" oh..i noticed another thing too!! which is when they code they don't like to read spec but when defect raised they look for fault in spec...great rite? can u imagine how much i love my job now?
About my boss something he said on meeting has caused people envy me and they think it is unfair to them. what abt it? Do you ever heard of when a boss praised an employee and it will ended up with people not happy with the employee? must be the employee know how to gosok rite, well no...employee didn't gosok ..just that the boss think that responsibility/accountability should be share among the team, not when issue raised someone has to hold it yet the entire team is accountable to it. What are the thing the boss should not said in front of everybody:
1- As a xxx professional you shouldn't make this mistake..oh mr. so and so i am not talking about you, i think you are doing it well. (not happy team member, didn't mr.so and so make mistake too? y when the person make mistake she/he don't get warn by the boss? see unhappy team members)
2- Why is this happening? Did you ever to question yourself that requirements gathered is not sufficient that causes this? Please don't blame on Mr. So and so, cause he/she definately feel bad now. I would like the team know this is the team responsible and manager should accounted to it. (more unhappy team members, cause she/he should do her job well, otherwise won't get scold by the boss)
Oh...after all the unhappy moment and assigned defect to me, how do i settle it? I was struggle however lucky i still have someone on my side to help me went thru all the issues. I called for a meeting with functional members and of coz the heart of the project...the project manager to discussed the issues and get answer rite away. Now they can't blame coz they attended the meeting and agreed with it...yoh...most word i used on the meeting was "It was discussed together and this was the solution earlier"," this is invalid scenario", "This has huge impact", "we gonna get it done by end of this week"..hahhahahaah!!!!!bad bad day!!
posted by Samlulu at 10:31 PM
26 comments
