stolen weekend
we're rolling out new software to a nationwide store this coming monday, and it seems like things are gonna be ugly.
just a few days before the actual rollout, our software showed several problems in pilot stores... it's crashing and trapping and it doesn't make sense why it's doing that.
we've been developing new functionalities very quickly, and we just kept slamming the codes with new things one after the other. we barely have enough time to use one version out in the field, here comes another one. needless to say, the software didn't have the chance to prove its stability, and we're adding new things on top of it.
so when something breaks, where should we start looking? which change introduced it? when? we keep tracking back when the functionality was introduced, but when we test the version prior to that one, it shows the same error. ok, so when did the problem really start?
it's becoming frustrating na. here we are with tight deadlines for the next version, of course, to add new stuff on it... pero we're still trying to make the base version work. will somebody stop the madness?
this is what happens when they want something fast. we develop at a factory-production-line pace, and skimp on the quality testing. we try to leave that to our SQA team, but i think they have tight deadlines as well, that they are not really creating quality test cases. *sigh*
when we address one thing, we introduce the possibility of breaking something else somewhere. why? because our software is not designed for the things that they want. but we still try to make things work. if we're given more time, i know we can fix things. during my first year at work, we're at a normal pace, and we seldom have problems like this. that's because we all take time to design the functionality well. we tend to test more scenarios because we have the time.
i'm just ranting. i'm tired. i've given up weekday nights. pati ba naman weekends? i was doing my timesheet a while ago, i've put in 65 hours this week. is this what i want in life?
papasok pa rin kami bukas. sunday. even God rested on sunday.
just a few days before the actual rollout, our software showed several problems in pilot stores... it's crashing and trapping and it doesn't make sense why it's doing that.
we've been developing new functionalities very quickly, and we just kept slamming the codes with new things one after the other. we barely have enough time to use one version out in the field, here comes another one. needless to say, the software didn't have the chance to prove its stability, and we're adding new things on top of it.
so when something breaks, where should we start looking? which change introduced it? when? we keep tracking back when the functionality was introduced, but when we test the version prior to that one, it shows the same error. ok, so when did the problem really start?
it's becoming frustrating na. here we are with tight deadlines for the next version, of course, to add new stuff on it... pero we're still trying to make the base version work. will somebody stop the madness?
this is what happens when they want something fast. we develop at a factory-production-line pace, and skimp on the quality testing. we try to leave that to our SQA team, but i think they have tight deadlines as well, that they are not really creating quality test cases. *sigh*
when we address one thing, we introduce the possibility of breaking something else somewhere. why? because our software is not designed for the things that they want. but we still try to make things work. if we're given more time, i know we can fix things. during my first year at work, we're at a normal pace, and we seldom have problems like this. that's because we all take time to design the functionality well. we tend to test more scenarios because we have the time.
i'm just ranting. i'm tired. i've given up weekday nights. pati ba naman weekends? i was doing my timesheet a while ago, i've put in 65 hours this week. is this what i want in life?
papasok pa rin kami bukas. sunday. even God rested on sunday.
posted by beng at
6:22 PM
2 Comments:
hope maayos na ung software nyo para maka rest na din kayo lahat. mababa din kasi productivity kapag ganyan.
By
eRLyN, at 8:09 AM
sinabi mo pa mare.
it looks like ok naman na as of yesterday, kaya kanina medyo relaxed sa trabaho. happy friday! =)
By
beng, at 9:35 PM
Post a Comment
<< Home