Re: OT: Bug versus Feature
I am not saying that MM cheated me, and I really do not want to debate whether drones have a bug or not. I was trying to define the difference between a bug and a feature. I was trying to educate people so they would not make false or inflammatory statements, nor assume that I was making false or inflammatory statements.
I am an application and processes designer. Although I started as a program writer and work closely with them, I no longer actually write the code. I am like an architect who designs the house that the builders build, or in this case an application or process that the coders code.
If I design something that is programmed and coded perfectly, but the result has a negative impact on the process, then I have designed a bug into the system. Just because the program was coded perfectly per the design doesn't mean the program doesn't have a bug.
If I design a house with a grand cathedral ceiling, that is built exactly to specifications but the result is undo stress upon a weight bearing wall that makes the ceiling unstable; is the house not defective? Does the house not have a "bug?"
The problems with most software applications and computer games are all design related. The application or the game has a bug because of poor design not because it was coded poorly.
The statement that a bug can not exist if the program was coded per design is false, invalid, and incorrect. A bug is a problem whether it is caused by poor coding or poor design. In fact, most bugs are caused by poor design which is why they are so hard to find.
If you don't accept this definition that is your choice, but then you are letting all the designers off the hook and do not complain when you receive poor quality product. I am in no way implying that SEIV is poor quality.
The only time I was not polite was in replying to what I perceived was a flame attack.
|