But its not just engineers who consent trouble with bad specs. Users have multitude of problems, too. Applications that ar supposed to be able to share data cant. A font which works fine on one system wont work on another. Computers cant talk to each other over a network. Or email messages come by unreadable. There are probably more ways for users to be hurt by bad specs than there are bad specs.
Ill look at some of the causes of these problems and suggest a few ideas for trying to make life better for engineers and users alike. afterwards all, if its easier for the engineer to get the code working correctly, its easier for the user to use the application the engineers developing.
Examples of problem standards
First Ill give some specific examples of problem standards Ive run into over the years. These are all real-life examples, precisely they may not all be problems anymore. Vendors may have actually fixed the problems I describe. I wouldnt bet on it, but its a possibility.
TIFF
The TIFF specification is one of the premiere specs I tangled with. We were working on paper a TIFF parser, and wrote it strictly to the specification. If a TIFF didnt assemble the specification exactly, our code would refuse to read the TIFF. Sadly, this needed to depart almost immediately, as we discovered that TIFFs produced by Adobe Photoshop (at that clip the owner of the standard, after theyd bought Aldus, who had originally created the...If you want to get a full essay, order it on our website: Ordercustompaper.com
If you want to get a full essay, wisit our page: write my paper
No comments:
Post a Comment