The Computer Journal
Typographic style is more than cosmetic
Communications of the ACM
ICICLE: groupware for code inspection
CSCW '90 Proceedings of the 1990 ACM conference on Computer-supported cooperative work
The user-centered iterative design of collaborative writing software
CHI '93 Proceedings of the INTERACT '93 and CHI '93 Conference on Human Factors in Computing Systems
Smalltalk with style
Literate Smalltalk Programming Using Hypertext
IEEE Transactions on Software Engineering
Back to the future: the story of Squeak, a practical Smalltalk written in itself
Proceedings of the 12th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Models of attention in computing and communication: from principles to applications
Communications of the ACM
Extreme Programming Explained: Embrace Change (2nd Edition)
Extreme Programming Explained: Embrace Change (2nd Edition)
Shared waypoints and social tagging to support collaboration in software development
CSCW '06 Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
Journal of Management Information Systems
Hi-index | 0.00 |
Contemporary development environments do not directly and explicitly support developers in having a conversation about the code they write and maintain. This problem is aggravated when geographically dispersed teams need to collaborate on development artifacts. CodeTalk allows developers to have conversations about source code elements. They can mark code sections they are concerned about and annotate them. These annotations provide entry points for an informal discourse about the strengths and weaknesses of these sections and developers can work towards a conclusion on how to proceed on the raised issues. A Squeak/Smalltalk implementation of CodeTalk was evaluated by several small development teams, indicating improvement in the informal assessment of code.