Impact of developer turnover on quality in open-source softwareSoftware developers' perceptions of productivitySpeculative reprogrammingGetting to Flow in Software DevelopmentRecommending a starting point for a programming task: an initial investigationDo developers discuss design?Persuasive technology in the real world: a study of long-term use of activity sensing devices for fitnessDegree-of-knowledge: Modeling a developer's knowledge of codeImproving software developers' fluency by recommending development environment commandsAutomatic categorization of bug reports using latent Dirichlet allocationSocially mediated technology awarenessFishtail: from task context to source code examplesICSE 2011 technical briefingsSupporting software history explorationDetermining relevancy: how software developers determine relevant information in feedsPeer interaction effectively, yet infrequently, enables programmers to discover new toolsHuman-centric software engineeringUnderstanding context: creating a lasting impact in experimental software engineering researchWhat is trust in a recommender for software development?Summarizing software artifacts: a case study of bug reportsA degree-of-knowledge model to capture source code familiarityUsing information fragments to answer the questions developers askCreating a cognitive metric of programming task difficultyA sketch of the programmer's coach: making programmers more effectiveAnswering conceptual queries with FerretDoes a programmer's activity indicate knowledge of code?Representing concerns in source codeUsing task context to improve programmer productivityQuestions programmers ask during software evolution tasksA focused learning environment for EclipseWho should fix this bug?Presenting crosscutting structure with active modelsCoping with an open bug repositoryAn empirical study of code clone genealogiesStrathcona example recommendation toolUsing structural context to recommend source code examplesRole-based refactoring of crosscutting concernsMylar: a degree-of-interest model for IDEsLearning from project history: a case study for software developmentRefactoring to aspects: an interactive approachStatic analysis to support the evolution of exception structure in object-oriented systemsConcern graphs: finding and describing concerns using structural program dependenciesManaging crosscutting concerns during software evolution tasks: an inquisitive studyExplicit programmingDoes aspect-oriented programming work?Implicit context: easing software evolution and reuseDesigning robust Java programs with exceptionsAn overview of the ICSE 2000 workshop programAtlas: a case study in building a web-based learning environment using aspect-oriented programmingAn initial assessment of aspect-oriented programmingPredicting memory use from a class diagram using dynamic informationVisualizing dynamic software system information through high-level modelsAn empirical study of static call graph extractorsOpen implementation design guidelinesOpen implementation analysis and designArchitecture for evolutionSoftware reflexion models: bridging the gap between source and high-level modelsLightweight source model extractionObjects in the life-cycleAn object-oriented hypermedia framework for command and control information systemsTowards a testing methodology for object-oriented systems