if you make a suggestion about hardware you need to follow proper thorough qa procedures.Originally Posted by SourceChild
You need to test in a wide range of machines, and a wide range of OS configurations.
And you need to provide sufficient detail so that someone else could create a replica system and either confirm or deny a problem or solution. This means providing detailed and accurate and credible information.
it means describing every step in a process or procedure.
Just because it works in your system does not mean it will work in anyone elses.
Single changes or omissions which seem obvious to you, are not obvious to anyone else.
Tests always need to be double and triple verified by other people with different configurations and different requirements.
And if you see problems - a single problem - it more than likely means it will not work well enough.
A single simple problem is often a killer- sure you might be able to make a hack - but
end users need trouble free and solutions that are as idiot proof as possible.
Hacking does not work.
Hacking is big trouble.
If you have to make any hacks to make something work - forget it.
I do not pursue solutions that involve modifying any standard hardware or software.
Reply With Quote