#24708
There is a direct line between the abstraction embodied in our code and the reality of the people who will come into contact with that code. Methodologies and managers are beside the point—a distraction from the real issue.
Read, Daniel. developer.star (2001). Articles>Usability>Programming
#13531
If We Build It, Will They Come? A Usability Test of Two Browser-based Embedded Help Systems 
The big problem with database-searching applications is that the user receives little feedback. Consider, for example, novice users starting to use Microsoft Word. The users want to right-justify a paragraph of text. Their efforts, either successful or unsuccessful, will be immediately apparent on the screen: The paragraph is either correctly justified or it isn't. However, a good-quality or a poor-quality search query used over a large database may retrieve 5,000 records, whether good or poor. How is the chemist to know whether the search query was effective and efficient? That is, how does the chemist know that the search query retrieved all and only the relevant records?
Grayling, Trevor. Technical Communication Online (2002). Articles>Usability>Programming
#20385
Product, Process, and Profit: The Politics of Usability in a Software Venture
In research and in practice,usability specialists commonly target the technology user-interfaces and help as the main arena for bringing about usability improvements. However, usability improvements depend on more than innovative and user-centered technical designs and implementations. Equally important for creating useful and usable software are the social and political forces that shape the development context. These forces give rise to leadership conflicts, factional disputes, renegade efforts, alliances and betrayals, all of which profoundly influence whether usability improvements will be supported and sustained within and across projects. This essay presents and analyzes a case history of a software start-up company in which usability achieved a Pyrrhic victory, triumphing only in the short run because of social and political forces.
Mirel, Barbara E. Journal of Computer Documentation (2000). Articles>Usability>Programming
#14133
In tandem with the theme of usability is the one of how to get (or help) programmers to communicate (to the user, to us...) – and the general tone is that, in effect, programmers really don't care about the end user's 'experience' of the software. If this is true, it occurs to me to wonder, WHY are programmers disinterested in usability?
#20180
The IT industry is maturing. Hopefully, this maturity will result in a slower introduction of new features, which in turn will let companies focus their attention and resources on making existing technology work better for users.
Nielsen, Jakob. Alertbox (2003). Articles>Usability>Programming>Software
#30010
What It Really Takes to Handle Exceptional Conditions 
Handling exceptions, errors, and alternative flows are a critical part of defining good use cases and designing good software. Correct handling of esceptional conditions is not only necessary for correct realization of requirements and for system reliability, but is also an important factor in usability. This paper details a systematic approach to the design of exception handling in object-oriented software.
Wirfs-Brock, Rebecca. Constantine and Lockwood (2003). Articles>Usability>Programming
#18292
Why GNOME Hackers Should Care about Usability
Usable Us'a*ble, a. Capable of being used. For such a simplistic definition, this encapsulates the fundamental goal of usability very well. Usable software is software that people can use; whether to write Email, play games or develop the next killer application. GNOME is many different things, but certainely one of its significant aspects is to provide an environment for users - for people. What a disappointment it should be when a user's ability to access one of the features we have coded is impaired or altogether halted because they don't understand how to manipulate the interface.
