The Style and Substance of API Names
Naming is a non-optional and cross-cutting design decision in professional and end-user programming activities. From assembly language to Yahoo Pipes, names are utilized for labeling and differentiation. Yet, we know little about how these names are selected or how naming impacts use and other aspec...
Saved in:
Published in | 2010 IEEE Symposium on Visual Languages and Human-Centric Computing pp. 259 - 260 |
---|---|
Main Author | |
Format | Conference Proceeding |
Language | English |
Published |
IEEE
01.09.2010
|
Subjects | |
Online Access | Get full text |
Cover
Loading…
Summary: | Naming is a non-optional and cross-cutting design decision in professional and end-user programming activities. From assembly language to Yahoo Pipes, names are utilized for labeling and differentiation. Yet, we know little about how these names are selected or how naming impacts use and other aspects of design. My research goal is to develop a theory of application programming interface (API) naming that bridges both software engineering and human-computer interaction. Towards this end, I am studying people (perceptions), information (naming strategies in the wild), and technology (name analysis algorithms and lightweight interactions to support naming decisions). |
---|---|
ISBN: | 1424484855 9781424484850 |
ISSN: | 1943-6092 1943-6106 |
DOI: | 10.1109/VLHCC.2010.48 |