BuzzerBeater Forums

Suggestions > Time to game is not correct above 100Hrs

Time to game is not correct above 100Hrs (thread closed)

Set priority
Show messages by
This Post:
22
199699.6 in reply to 199699.4
Date: 10/30/2011 9:19:48 PM
Overall Posts Rated:
766766
In IT a bug is something which doesn't work how it was to be intended. Some developers will even suggest that a bug is only something which 'breaks' the system, although this is generally an old-school view on things.
If the clock showed 10 hrs to a game, and in fact, it was 20 hrs to a game, that would be a bug.

Us developers get a bit testy about people calling our hard slaved implementations 'bugs'. (Especially when you turn around to the customer, shove the specification doco in his face and say 'Thats what you bloody asked for!')....

So yes. Bug or no bug,
its a good suggestion. :)


This Post:
00
199699.7 in reply to 199699.6
Date: 11/1/2011 4:16:37 AM
Overall Posts Rated:
105105
I don't see it this way.
If a design is wrong, than it is a bug in the design.

Anyway, I enjoy your product (this game).
So, keep up the good work!!!

[Definitions are not that important, improving what can be improved is the goal]

This Post:
33
199699.8 in reply to 199699.7
Date: 11/1/2011 5:40:57 AM
Overall Posts Rated:
3535
Well, if you don't see it that way then you're wrong.
Sorry to break that to you.
It's not a matter of opinions here.

This Post:
00
199699.9 in reply to 199699.8
Date: 11/1/2011 10:05:25 PM
Overall Posts Rated:
766766
the definition of a bug is a contentious issue not just within Buzzerbeater. Where i work people throw the word 'bug' around very loosely. When someone tells me there is a 'bug' i usually get very angry, because 99% of the time, ive just coded what they have asked for and they havent told me well enough.

The orange juice example - Client asks for a glass of orange juice. I give them Brand X orange Juice in a glass. They reply saying 'oh but i wanted Brand Y orange juice'.

well... they didnt ask for Brand Y, they just said 'a glass of orange juice'.... this is not a bug.

So seeing as though the english language is a very contentious language to learn, might i suggest that instead of using the word 'bug' - use the word 'Flaw' or.. 'problem'. or... 'something not quite right'.

Developers will love you more :)



This Post:
00
199699.10 in reply to 199699.9
Date: 11/2/2011 2:41:50 AM
Overall Posts Rated:
105105
the definition of a bug is a contentious issue not just within Buzzerbeater. Where i work people throw the word 'bug' around very loosely. When someone tells me there is a 'bug' i usually get very angry, because 99% of the time, ive just coded what they have asked for and they havent told me well enough.
Then it is a bug at the System-Requirements.

The orange juice example - Client asks for a glass of orange juice. I give them Brand X orange Juice in a glass. They reply saying 'oh but i wanted Brand Y orange juice'.
well... they didnt ask for Brand Y, they just said 'a glass of orange juice'.... this is not a bug.
This is a "bug" at the customer request. As the customer does never has bugs, it is still the seller fault. :+)

So seeing as though the english language is a very contentious language to learn, might i suggest that instead of using the word 'bug' - use the word 'Flaw' or.. 'problem'. or... 'something not quite right'.
Developers will love you more :)
I didn't blame anyone, but it is a bug - SyRS, design or implementation. It doesn't matter.
The clock is supposed to display... the correct time.
The purpose of opening a bug is not to blame someone, but for improving the product current fault behavior.

It is funny, I've just wanted this feature fixed, and haven't thought it will cause too much noise, as it is non-mistakable a bug/wrong-behavior/whatever, and one that can be fixed easily and fast.
Instead the discussion came into defining what a bug is... :+)
Not that it annoys me or something, it is just surprising...

This Post:
00
199699.11 in reply to 199699.10
Date: 11/2/2011 4:00:25 AM
Overall Posts Rated:
237237
Then it is a bug at the System-Requirements.

It is NOT a bug. The clock showing 99:59 is by design of the developers. Whats to say it is "wrong"? The BBs could have wanted it this way.

This is a "bug" at the customer request. As the customer does never has bugs, it is still the seller fault. :+)


It is NOT a bug. It is the customer being unclear about specification requirements. This is not sales and customer service. In IT the customer is NOT always right. It is more often just a matter of opinion and what angle you look at it.


So stop calling it a bug. Calling it a bug makes it sound a lot more dramatic than it should and implies that the BBs have done something wrong with their programming. This is clearly not the case as it is showing that by design.

It is an enhancement request.


This Post:
00
199699.12 in reply to 199699.10
Date: 11/2/2011 4:08:11 AM
Overall Posts Rated:
13361336
Then it is a bug at the System-Requirements.
Someone just explained to you what a bug is. You are trying to imply here that you have some experience in programming. How can you not see a difference in design flaw and a bug.

This Post:
00
199699.13 in reply to 199699.10
Date: 11/2/2011 6:30:23 AM
Overall Posts Rated:
766766
See now you're just teasing!

I did say that developers hate the word bug, thats why its such a big deal.

Ive been in meetings at work where people have mis-used the word bug and people have like, stood up, yelled, walked out, refused to deal with them until they apologise for calling it a bug. Its a such a funny thing.

Even in the contract documentation, they refuse to use the word 'bug' because it causes such issues. They use the word 'defect' instead.


This Post:
00
199699.14 in reply to 199699.10
Date: 11/2/2011 6:53:17 AM
Overall Posts Rated:
587587
The clock is supposed to display... the correct time.

It is also supposed to be easy to understand and to nicely fit into the box where it is displayed. The current clock fulfills these requirements, and we should believe it follows the design choice made by the developers (given how visible it is they otherwise would have figured that the clock is wrong and fixed it by now). A bug it is not.

This Post:
00
199699.15 in reply to 199699.14
Date: 11/2/2011 7:31:43 AM
Overall Posts Rated:
105105
It is also supposed to be easy to understand
So, when it says 99:99 it is "easy to understand that it is 6 days and 3 Hrs? No it is not.

to nicely fit into the box where it is displayed.
It can feet easily. There are two characters and separator in the box, so even w/o changing the box size (although there is no reason why it should stay the same size), you can write - 6D:3H.

we should believe it follows the design choice made by the developers (given how visible it is they otherwise would have figured that the clock is wrong and fixed it by now). A bug it is not.
It does NOT show the correct time!!! This is a bug! It does not matter where the bug is. The customer see a clock and it is not accurate => bug in the product.
I have clocks that show the time correctly two times a day (figure how). Isn't it an "HW" bug? Yes it is most definitely is.

It is not a critical or a hard bug, and it almost redundant, but a bug it is.

This Post:
00
199699.16 in reply to 199699.15
Date: 11/2/2011 7:37:57 AM
Overall Posts Rated:
105105
Product that claims to display something (and this is exactly what the clock above claims to do), and does not display the correct time has a bug.

It does not matter whether it is implementation, design, SyRS bug. It is still a bug!

The developers did not mean that it will display a wrong time.

Advertisement