shame to my tester or me?
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
kdgupta87 wrote:
suddenly in 13 april my project stop sending data, which is one of its main functionality
Here you accidentally already wrote the solution. It's not a bug, stopping to send stuff is a feature. And welcome to the ever growing club of people who have learned the value of date datatypes/classes over some casual string manipulations :)
At least artificial intelligence already is superior to natural stupidity
-
kdgupta87 wrote:
suddenly in 13 april my project stop sending data, which is one of its main functionality
Here you accidentally already wrote the solution. It's not a bug, stopping to send stuff is a feature. And welcome to the ever growing club of people who have learned the value of date datatypes/classes over some casual string manipulations :)
At least artificial intelligence already is superior to natural stupidity
-
why all over the world, everyone not following the same date time format, they should think about poor programmers like me :confused:
That's another lesson to be learned the hard way. Users never waste any thought about helping us. For them you are a wizard and they don't want to know what sinister things you have to do for your magic. But they still want the miracles yesterday, for free and without any inconveniences :)
At least artificial intelligence already is superior to natural stupidity
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
There's a lesson to learn here about using an unambiguous date format. If you have to use string date transfer at all, that is, but for passing data between applications that is often the case (e.g. if you're using web services or similar protocols). I use either 2012-05-02 or 2-May-2012, usually the former, if I'm saving or passing dates and need to be able to understand them at the other end. Your tester should have tested this, though. That's the point of having a tester.
-
There's a lesson to learn here about using an unambiguous date format. If you have to use string date transfer at all, that is, but for passing data between applications that is often the case (e.g. if you're using web services or similar protocols). I use either 2012-05-02 or 2-May-2012, usually the former, if I'm saving or passing dates and need to be able to understand them at the other end. Your tester should have tested this, though. That's the point of having a tester.
Sure, but now we also have a tester and a developer who will probably not forget this in the future. The sum of such experiences is what counts. People always learn more by their mistakes than by success.
At least artificial intelligence already is superior to natural stupidity
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
-
why all over the world, everyone not following the same date time format, they should think about poor programmers like me :confused:
We do; it's called ISO 8601.
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
It also sounds like your app is running in "real time", but likely when developed and tested, it did not have a "real time" environment to work with. This is usually addressed with some form of a declared test operation in the "real time" environment. These can often last weeks and even months, before all issues are uncovered.
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
Reminds me of some work I did during the Y2K fiasco. I spent months working on some really old code to make it Y2K compliant. Then on January 1, 2000, everything ran smoothly! -- not a single problem. I practically broke my arm patting myself on the back. A couple of months later on February 29, 2000, everything crashed. You see, the year 2000 was a leap year, but the year 1900 was not. My conversion of 1900 dates to 2000 dates did not take that into account. Epic fail. Fortunately, I had already collected my contract fees. :-D
-NP Never underestimate the creativity of the end-user.
-
Sure, but now we also have a tester and a developer who will probably not forget this in the future. The sum of such experiences is what counts. People always learn more by their mistakes than by success.
At least artificial intelligence already is superior to natural stupidity
Oh, that's definitely true. And it sounds like it was a relatively low tariff place to make the mistake (easy to notice, easy to find the cause and fix, not a critical system), so all's good in the end. But it is more a tester mistake than a dev mistake, in my opinion.
-
Reminds me of some work I did during the Y2K fiasco. I spent months working on some really old code to make it Y2K compliant. Then on January 1, 2000, everything ran smoothly! -- not a single problem. I practically broke my arm patting myself on the back. A couple of months later on February 29, 2000, everything crashed. You see, the year 2000 was a leap year, but the year 1900 was not. My conversion of 1900 dates to 2000 dates did not take that into account. Epic fail. Fortunately, I had already collected my contract fees. :-D
-NP Never underestimate the creativity of the end-user.
-
Ooh, painful. Did you feel guilty enough to fix it for them even though your contract was over?
Well, it kinda fixed itself...about midnight on that day as I recall. :laugh: I must not have made too bad of impression as I eventually received another contract to upgrade all of their software to use C# front-ends and SQL server back-ends, so the whole date thing was never an issue after that day.
-NP Never underestimate the creativity of the end-user.
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
Both. It isn't exactly hidden that people use different formats across the world - even some Americans are aware of it. It's not exactly difficult to work with different formats these days either. And are you saying that it took less that twelve days to develop the software? Or that you didn't test your own code at all for three weeks of each month? It's a rookie mistake, for both developer and the tester - it doesn't bode well for the long term reliabilty of the software from where I'm sitting.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
Both. It isn't exactly hidden that people use different formats across the world - even some Americans are aware of it. It's not exactly difficult to work with different formats these days either. And are you saying that it took less that twelve days to develop the software? Or that you didn't test your own code at all for three weeks of each month? It's a rookie mistake, for both developer and the tester - it doesn't bode well for the long term reliabilty of the software from where I'm sitting.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
Shame on tester if the software requirement/design requirement mentioned the format of the date. Shame on you if it didn't. If your tester doesn't have an up to date requirement specification/design document he's not to blame, but you are. It's pointless having a tester if you don't give him something to test the software against. Sure, he might find some bugs but he'll miss most.
"Program testing can be used to show the presence of bugs, but never to show their absence." << please vote!! >>
-
it was just a plugin in existing software. And yes its a very silly mistake by me(hope my boss will not see tht), but as long as i can pass responsibility to tester why i care :laugh: :laugh: :laugh:
And this is exactly where a lot of stuff goes wrong...
kdgupta87 wrote:
it was just a ...
and
kdgupta87 wrote:
but as long as i can pass responsibility to tester why i care
Take what you do seriously, and take the responsibilty for what you do. Those smily icons aside, with a mentality like yours you wouldn't last long if you were ever to work with me...
-
And this is exactly where a lot of stuff goes wrong...
kdgupta87 wrote:
it was just a ...
and
kdgupta87 wrote:
but as long as i can pass responsibility to tester why i care
Take what you do seriously, and take the responsibilty for what you do. Those smily icons aside, with a mentality like yours you wouldn't last long if you were ever to work with me...
:thumbsup:
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
it was just a plugin in existing software. And yes its a very silly mistake by me(hope my boss will not see tht), but as long as i can pass responsibility to tester why i care :laugh: :laugh: :laugh:
I have to agree with cptKoala - take responsibility for your mistakes. If nothing else, you may want your tester on your side, rather than against you. If you blame him for your mistakes, you won't makes friends there...
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
I start a project in 2nd april, i finished it 8th april, the tester tested the project and pass 9th april and client get happy on that, suddenly in 13 april my project stop sending data, which is one of its main functionality. i was wonder why why my code works only 5 days, what happens, there is nothing changed why data was not sending now. suddenly i discovered what was the fault, because from 1st may it again start to work and i am confident it will work until 12th may, and then it will again stop :-O :-O :-O . i think u already get the hint, problem was date time format in server and client side. mm-dd-yy and dd-mm-yy , for that it will only work 1st 12 days of a month, not bad :D
Well obviously its your fault! Testers are not there to test for programmer errors, they are there for testing whether or not the system meets the specification. And if you think you can get away with blaming the testers for your own lack of care and commitment, then you are horrendously wrong. Whenever writing date related code I always make sure I unit test for formats because the system can be used in any locale, I don't see how its the tester's fault. Its just common sense and its about sense of ownership for your work.
