var bibbase_data = {"data":"\"Loading..\"\n\n
\n\n \n\n \n\n \n \n\n \n\n \n \n\n \n\n\n
\n generated by\n \n \"bibbase.org\"\n\n \n
\n\n
\n\n \n\n\n
\n \n\n Excellent! Next, you can embed this page using\n one of several\n options.\n
\n\n
\n \n\n

To the site owner:

\n\n

Action required! Mendeley is changing its\n API. In order to keep using Mendeley with BibBase past April\n 14th, you need to:\n

    \n
  1. renew the authorization for BibBase on Mendeley, and
  2. \n
  3. update the BibBase URL\n in your page the same way you did when you initially set up\n this page.
  4. \n

\n\n

\n \n \n Fix it now\n

\n
\n\n
\n\n\n
\n \n \n
\n
\n  \n 1. Journal\n \n \n (9)\n \n \n
\n
\n \n \n
\n
\n  \n 2019\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n What Predicts Software Developers' Productivity?.\n \n\n\n \n Murphy-Hill, E.; Jaspan, C.; Sadowski, C.; Shepherd, D. C.; Phillips, M.; Winter, C.; Dolan, A. K.; Smith, E. K.; and Jorde, M. A.\n\n\n \n\n\n\n Transactions on Software Engineering. 2019.\n \n\n\n\n
\n\n\n\n \n \n \"WhatPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n  \n \n 8 downloads\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{47853,\ntitle\t= {What Predicts Software Developers' Productivity?},\nauthor\t= {Emerson Murphy-Hill and Ciera Jaspan and Caitlin Sadowski and David C. Shepherd and Michael Phillips and Collin Winter and Andrea Knight Dolan and Edward K. Smith and Matthew A. Jorde},\nyear\t= {2019},\njournal\t= {Transactions on Software Engineering},\nhowpublished = {1. Journal},\nurl = {https://people.engr.ncsu.edu/ermurph3/papers/tse19.pdf},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2017\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Gender differences and bias in open source: Pull request acceptance of women versus men.\n \n\n\n \n Terrell, J.; Kofink, A.; Middleton, J.; Rainear, C.; Murphy-Hill, E.; Parnin, C.; and Stallings, J.\n\n\n \n\n\n\n PeerJ Computer Science, 3: e111. 2017.\n \n\n\n\n
\n\n\n\n \n \n \"GenderPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{terrell2017gender,\n  title={Gender differences and bias in open source: Pull request acceptance of women versus men},\n  author={Terrell, Josh and Kofink, Andrew and Middleton, Justin and Rainear, Clarissa and Murphy-Hill, Emerson and Parnin, Chris and Stallings, Jon},\n  journal={PeerJ Computer Science},\n  volume={3},\n  pages={e111},\n  year={2017},\n  url = {https://peerj.com/articles/cs-111/},\n  howpublished = {1. Journal},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2016\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Design and Evaluation of a Multi-Recommendation System for Local Code Search.\n \n\n\n \n Ge, X.; Shepherd, D. C.; Damevski, K.; and Murphy-Hill, E.\n\n\n \n\n\n\n Journal of Visual Languages and Computing. 2016.\n \n\n\n\n
\n\n\n\n \n \n \"DesignPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{Ge2016Design,\n    author = {Ge, Xi and Shepherd, David C. and Damevski, Kostadin and Murphy-Hill, Emerson},\n    citeulike-article-id = {14104539},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/jvlc16.pdf},\n    journal = {Journal of Visual Languages and Computing},\n    posted-at = {2016-07-29 23:33:32},\n    priority = {2},\n    title = {{Design and Evaluation of a Multi-Recommendation System for Local Code Search}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/jvlc16.pdf},\n    year = {2016},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2015\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Will the ``Phisher-Men'' Reel You In?: Assessing Individual Differences in a Phishing Detection Task.\n \n\n\n \n Welk, A. K.; Hong, K. W.; Zielinska, O. A.; Tembe, R.; Murphy-Hill, E.; and Mayhorn, C. B.\n\n\n \n\n\n\n International Journal of Cyber Behavior, Psychology and Learning (IJCBPL), 5(4): 1–17. 2015.\n \n\n\n\n
\n\n\n\n \n \n \"WillPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{welk2015will,\n    author = {Welk, Allaire K. and Hong, Kyung W. and Zielinska, Olga A. and Tembe, Rucha and Murphy-Hill, Emerson and Mayhorn, Christopher B.},\n    citeulike-article-id = {13933980},\n    citeulike-linkout-0 = {http://dx.doi.org/10.4018/IJCBPL.2015100101},\n    doi = {10.4018/IJCBPL.2015100101},\n    journal = {International Journal of Cyber Behavior, Psychology and Learning (IJCBPL)},\n    keywords = {phishing},\n    number = {4},\n    pages = {1--17},\n    posted-at = {2016-02-16 20:42:30},\n    priority = {0},\n    publisher = {IGI Global},\n    title = {{Will the ``Phisher-Men'' Reel You In?: Assessing Individual Differences in a Phishing Detection Task}},\n    url = {http://dx.doi.org/10.4018/IJCBPL.2015100101},\n    volume = {5},\n    year = {2015},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n How Do Users Discover New Tools in Software Development and Beyond?.\n \n\n\n \n Murphy-Hill, E.; Lee, D. Y.; Murphy, G. C.; and McGrenere, J.\n\n\n \n\n\n\n Computer Supported Cooperative Work. 2015.\n \n\n\n\n
\n\n\n\n \n \n \"HowPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n  \n \n 4 downloads\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{MurphyHill2015How,\n    author = {Murphy-Hill, Emerson and Lee, Da Y. and Murphy, Gail C. and McGrenere, Joanna},\n    citeulike-article-id = {13679697},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1007/s10606-015-9230-9},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/jcscw15.pdf},\n    doi = {10.1007/s10606-015-9230-9},\n    journal = {Computer Supported Cooperative Work},\n    keywords = {adoption},\n    posted-at = {2015-07-21 20:42:17},\n    priority = {0},\n    title = {{How Do Users Discover New Tools in Software Development and Beyond?}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/jcscw15.pdf},\n    year = {2015},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2014\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n The Design Space of Bug Fixes and How Developers Navigate It.\n \n\n\n \n Murphy-Hill, E.; Zimmermann, T.; Bird, C.; and Nagappan, N.\n\n\n \n\n\n\n Transactions on Software Engineering. 2014.\n \n\n\n\n
\n\n\n\n \n \n \"ThePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n  \n \n 2 downloads\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{MurphyHill2014Design,\n    author = {Murphy-Hill, Emerson and Zimmermann, Thomas and Bird, Christian and Nagappan, Nachiappan},\n    citeulike-article-id = {13350008},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/TSE.2014.2357438},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/Design\\_of\\_Bug\\_Fixes\\_TSE.pdf},\n    doi = {10.1109/TSE.2014.2357438},\n    journal = {Transactions on Software Engineering},\n    keywords = {bugs},\n    posted-at = {2014-09-07 18:25:45},\n    priority = {2},\n    title = {{The Design Space of Bug Fixes and How Developers Navigate It}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/Design\\_of\\_Bug\\_Fixes\\_TSE.pdf},\n    year = {2014},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Degree-of-Knowledge: Modeling a Developer's Knowledge of Code.\n \n\n\n \n Fritz, T.; Murphy, G. C.; Murphy-Hill, E.; Ou, J.; and Hill, E.\n\n\n \n\n\n\n Transactions on Software Engineering and Methodology. 2014.\n \n\n\n\n
\n\n\n\n \n \n \"Degree-of-Knowledge:Paper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{Fritz2014DegreeofKnowledge,\n    author = {Fritz, Thomas and Murphy, Gail C. and Murphy-Hill, Emerson and Ou, Jingwen and Hill, Emily},\n    citeulike-article-id = {13110302},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2512207},\n    doi = {10.1145/2512207},\n    journal = {Transactions on Software Engineering and Methodology},\n    keywords = {self},\n    posted-at = {2014-03-18 21:15:05},\n    priority = {2},\n    title = {{Degree-of-Knowledge: Modeling a Developer's Knowledge of Code}},\n    url = {http://dx.doi.org/10.1145/2512207},\n    year = {2014},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2013\n \n \n (4)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Comparing Approaches to Analyze Refactoring Activity on Software Repositories.\n \n\n\n \n Soares, G.; Gheyi, R.; Murphy-Hill, E.; and Johnson, B.\n\n\n \n\n\n\n Journal of Systems and Software, 86(4): 1006–1022. April 2013.\n \n\n\n\n
\n\n\n\n \n \n \"ComparingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{Soares2013Comparing,\n    abstract = {{Some approaches have been used to investigate evidence on how developers refactor their code, whether refactorings activities may decrease the number of bugs, or improve developers' productivity. However, there are some contradicting evidence in previous studies. For instance, some investigations found evidence that if the number of refactoring changes increases in the preceding time period the number of defects decreases, different from other studies. They have used different approaches to evaluate refactoring activities. Some of them identify committed behavior-preserving transformations in software repositories by using manual analysis, commit messages, or dynamic analysis. Others focus on identifying which refactorings are applied between two programs by using manual inspection or static analysis. In this work, we compare three different approaches based on manual analysis, commit message (Ratzinger's approach) and dynamic analysis (SafeRefactor's approach) to detect whether a pair of versions determines a refactoring, in terms of behavioral preservation. Additionally, we compare two approaches (manual analysis and Ref-Finder) to identify which refactorings are performed in each pair of versions. We perform both comparisons by evaluating their accuracy, precision, and recall in a randomly selected sample of 40 pairs of versions of JHotDraw, and 20 pairs of versions of Apache Common Collections. While the manual analysis presents the best results in both comparisons, it is not as scalable as the automated approaches. Ratzinger's approach is simple and fast, but presents a low recall; differently, SafeRefactor is able to detect most applied refactorings, although limitations in its test generation backend results for some kinds of subjects in low precision values. Ref-Finder presented a low precision and recall in our evaluation.}},\n    author = {Soares, Gustavo and Gheyi, Rohit and Murphy-Hill, Emerson and Johnson, Brittany},\n    citeulike-article-id = {11724308},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/jss12.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1016/j.jss.2012.10.040},\n    doi = {10.1016/j.jss.2012.10.040},\n    issn = {01641212},\n    journal = {Journal of Systems and Software},\n    keywords = {refactoring, self},\n    month = apr,\n    number = {4},\n    pages = {1006--1022},\n    posted-at = {2013-10-16 17:01:29},\n    priority = {2},\n    title = {{Comparing Approaches to Analyze Refactoring Activity on Software Repositories}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/jss12.pdf},\n    volume = {86},\n    year = {2013},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n
\n Some approaches have been used to investigate evidence on how developers refactor their code, whether refactorings activities may decrease the number of bugs, or improve developers' productivity. However, there are some contradicting evidence in previous studies. For instance, some investigations found evidence that if the number of refactoring changes increases in the preceding time period the number of defects decreases, different from other studies. They have used different approaches to evaluate refactoring activities. Some of them identify committed behavior-preserving transformations in software repositories by using manual analysis, commit messages, or dynamic analysis. Others focus on identifying which refactorings are applied between two programs by using manual inspection or static analysis. In this work, we compare three different approaches based on manual analysis, commit message (Ratzinger's approach) and dynamic analysis (SafeRefactor's approach) to detect whether a pair of versions determines a refactoring, in terms of behavioral preservation. Additionally, we compare two approaches (manual analysis and Ref-Finder) to identify which refactorings are performed in each pair of versions. We perform both comparisons by evaluating their accuracy, precision, and recall in a randomly selected sample of 40 pairs of versions of JHotDraw, and 20 pairs of versions of Apache Common Collections. While the manual analysis presents the best results in both comparisons, it is not as scalable as the automated approaches. Ratzinger's approach is simple and fast, but presents a low recall; differently, SafeRefactor is able to detect most applied refactorings, although limitations in its test generation backend results for some kinds of subjects in low precision values. Ref-Finder presented a low precision and recall in our evaluation.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Adoption and Use of Java Generics.\n \n\n\n \n Parnin, C.; Bird, C.; and Murphy-Hill, E.\n\n\n \n\n\n\n , 18(6): 1047–1089. 2013.\n \n\n\n\n
\n\n\n\n \n \n \"AdoptionPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{Parnin2013Adoption,\n    abstract = {{Support for generic programming was added to the Java language in 2004, representing perhaps the most significant change to one of the most widely used programming languages today. Researchers and language designers anticipated this addition would relieve many long-standing problems plaguing developers, but surprisingly, no one has yet measured how generics have been adopted and used in practice. In this paper, we report on the first empirical investigation into how Java generics have been integrated into open source software by automatically mining the history of 40 popular open source Java programs, traversing more than 650 million lines of code in the process. We evaluate five hypotheses and research questions about how Java developers use generics. For example, our results suggest that generics sometimes reduce the number of type casts and that generics are usually adopted by a single champion in a project, rather than all committers. We also offer insights into why some features may be adopted sooner and others features may be held back.}},\n    author = {Parnin, Chris and Bird, Christian and Murphy-Hill, Emerson},\n    booktitle = {Empirical Software Engineering},\n    citeulike-article-id = {12716832},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/ese12.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1007/s10664-012-9236-6},\n    citeulike-linkout-2 = {http://link.springer.com/article/10.1007/s10664-012-9236-6},\n    doi = {10.1007/s10664-012-9236-6},\n    keywords = {programming\\_languages, self},\n    number = {6},\n    pages = {1047--1089},\n    posted-at = {2013-10-16 17:00:48},\n    priority = {2},\n    publisher = {Springer US},\n    title = {{Adoption and Use of Java Generics}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/ese12.pdf},\n    volume = {18},\n    year = {2013},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n
\n Support for generic programming was added to the Java language in 2004, representing perhaps the most significant change to one of the most widely used programming languages today. Researchers and language designers anticipated this addition would relieve many long-standing problems plaguing developers, but surprisingly, no one has yet measured how generics have been adopted and used in practice. In this paper, we report on the first empirical investigation into how Java generics have been integrated into open source software by automatically mining the history of 40 popular open source Java programs, traversing more than 650 million lines of code in the process. We evaluate five hypotheses and research questions about how Java developers use generics. For example, our results suggest that generics sometimes reduce the number of type casts and that generics are usually adopted by a single champion in a project, rather than all committers. We also offer insights into why some features may be adopted sooner and others features may be held back.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Interactive Ambient Visualizations for Soft Advice.\n \n\n\n \n Murphy-Hill, E.; Barik, T.; and Black, A. P.\n\n\n \n\n\n\n Information Visualization,1473871612469020+. March 2013.\n \n\n\n\n
\n\n\n\n \n \n \"InteractivePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{MurphyHill2013Interactive,\n    abstract = {{Some software packages offer the user soft advice: recommendations that are intended to help the user create high-quality artifacts but which may turn out to be bad advice. It is left to the user to determine whether the soft advice really will improve quality and to decide whether to adopt it. Visualizations can help the user in making this decision, but we believe that conventional visualizations are less than ideal. In this article, we describe an interactive ambient visualization to help users identify, understand, and interpret soft advice. Our visualization was developed to help programmers interpret code smells, which are indications that a software project may be suffering from design problems. We describe a laboratory experiment with 12 programmers that tests several hypotheses about our visualization. The findings suggest that our tool helps programmers to identify smells more effectively and to make more informed judgments about the design of the program under development. We then describe an application of our visualization technique in another domain: an English style and grammar advisor. This second application suggests that our technique can be applied to several domains and also suggests how the technique must be varied to make it domain specific.}},\n    author = {Murphy-Hill, Emerson and Barik, Titus and Black, Andrew P.},\n    citeulike-article-id = {12716837},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/iv13.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1177/1473871612469020},\n    citeulike-linkout-2 = {http://ivi.sagepub.com/content/early/2013/03/03/1473871612469020.abstract},\n    citeulike-linkout-3 = {http://ivi.sagepub.com/content/early/2013/03/03/1473871612469020.full.pdf},\n    day = {06},\n    doi = {10.1177/1473871612469020},\n    issn = {1473-8724},\n    journal = {Information Visualization},\n    keywords = {refactoring, self},\n    month = mar,\n    pages = {1473871612469020+},\n    posted-at = {2013-10-16 17:00:37},\n    priority = {2},\n    publisher = {SAGE Publications},\n    title = {{Interactive Ambient Visualizations for Soft Advice}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/iv13.pdf},\n    year = {2013},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n
\n Some software packages offer the user soft advice: recommendations that are intended to help the user create high-quality artifacts but which may turn out to be bad advice. It is left to the user to determine whether the soft advice really will improve quality and to decide whether to adopt it. Visualizations can help the user in making this decision, but we believe that conventional visualizations are less than ideal. In this article, we describe an interactive ambient visualization to help users identify, understand, and interpret soft advice. Our visualization was developed to help programmers interpret code smells, which are indications that a software project may be suffering from design problems. We describe a laboratory experiment with 12 programmers that tests several hypotheses about our visualization. The findings suggest that our tool helps programmers to identify smells more effectively and to make more informed judgments about the design of the program under development. We then describe an application of our visualization technique in another domain: an English style and grammar advisor. This second application suggests that our technique can be applied to several domains and also suggests how the technique must be varied to make it domain specific.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n The Reaction of Open-Source Projects to New Language Features.\n \n\n\n \n Kim, D.; Murphy-Hill, E.; Parnin, C.; Bird, C.; and Garcia, R.\n\n\n \n\n\n\n Journal of Object Technology. 2013.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{Kim2013Reaction,\n    author = {Kim, Donghoon and Murphy-Hill, Emerson and Parnin, Chris and Bird, Christian and Garcia, Ronald},\n    citeulike-article-id = {12717125},\n    editor = {Vitek, Jan},\n    journal = {Journal of Object Technology},\n    keywords = {programming\\_languages, self},\n    posted-at = {2013-10-16 15:09:14},\n    priority = {2},\n    title = {{The Reaction of Open-Source Projects to New Language Features}},\n    year = {2013},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2011\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Programmer-Friendly Refactoring Errors.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n IEEE Transactions on Software Engineering, 99(PrePrints). 2011.\n \n\n\n\n
\n\n\n\n \n \n \"Programmer-FriendlyPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{MurphyHill2011ProgrammerFriendly,\n    abstract = {{Refactoring tools, common to many integrated development environments, can help programmers to restructure their code. These tools sometimes refuse to restructure the programmer's code, instead giving the programmer a textual error message that she must decode if she wishes to understand the reason for the tool's refusal, and what corrective action to take. This article describes a graphical alternative to textual error messages called Refactoring Annotations. It reports on two experiments, one using an integrated development environment and the other using paper mockups, that show that programmers can use Refactoring Annotations to quickly and accurately understand the cause of refactoring errors.}},\n    address = {Los Alamitos, CA, USA},\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    citeulike-article-id = {11237059},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/tse11.pdf},\n    citeulike-linkout-1 = {http://doi.ieeecomputersociety.org/10.1109/TSE.2011.110},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1109/tse.2011.110},\n    doi = {10.1109/tse.2011.110},\n    issn = {0098-5589},\n    journal = {IEEE Transactions on Software Engineering},\n    keywords = {program\\_analysis, refactoring, self},\n    number = {PrePrints},\n    posted-at = {2013-10-16 17:30:32},\n    priority = {2},\n    publisher = {IEEE Computer Society},\n    title = {{Programmer-Friendly Refactoring Errors}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/tse11.pdf},\n    volume = {99},\n    year = {2011},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n
\n Refactoring tools, common to many integrated development environments, can help programmers to restructure their code. These tools sometimes refuse to restructure the programmer's code, instead giving the programmer a textual error message that she must decode if she wishes to understand the reason for the tool's refusal, and what corrective action to take. This article describes a graphical alternative to textual error messages called Refactoring Annotations. It reports on two experiments, one using an integrated development environment and the other using paper mockups, that show that programmers can use Refactoring Annotations to quickly and accurately understand the cause of refactoring errors.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2008\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Refactoring Tools: Fitness for Purpose.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n IEEE Software, 25(5): 38–44. 2008.\n \n\n\n\n
\n\n\n\n \n \n \"RefactoringPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{MurphyHill2008Refactoring,\n    abstract = {{Refactoring is the process of changing software's structure while preserving its external behavior. Refactoring tools can improve the speed and accuracy with which developers create and maintain software-but only if they are used. In practice, tools are not used as much as they could be; this seems to be because sometimes they do not align with the refactoring tactic preferred by most programmers, a tactic the authors call "floss refactoring." They propose five principles that characterize successful floss-refactoring tools - principles that can help programmers to choose the most appropriate refactoring tools and also help toolsmiths to design tools that fit the programmer's purpose.}},\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    citeulike-article-id = {11236957},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/IEEESoftware08.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1109/ms.2008.123},\n    citeulike-linkout-2 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=4602672},\n    doi = {10.1109/ms.2008.123},\n    institution = {Portland State Univ., Portland, OR},\n    issn = {0740-7459},\n    journal = {IEEE Software},\n    keywords = {refactoring, self},\n    number = {5},\n    pages = {38--44},\n    posted-at = {2013-10-16 17:33:17},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{Refactoring Tools: Fitness for Purpose}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/IEEESoftware08.pdf},\n    volume = {25},\n    year = {2008},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n
\n Refactoring is the process of changing software's structure while preserving its external behavior. Refactoring tools can improve the speed and accuracy with which developers create and maintain software-but only if they are used. In practice, tools are not used as much as they could be; this seems to be because sometimes they do not align with the refactoring tactic preferred by most programmers, a tactic the authors call \"floss refactoring.\" They propose five principles that characterize successful floss-refactoring tools - principles that can help programmers to choose the most appropriate refactoring tools and also help toolsmiths to design tools that fit the programmer's purpose.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2007\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Component-Based End-User Database Design for Ecologists.\n \n\n\n \n Cushing, J. B.; Nadkarni, N.; Finch, M.; Fiala, A.; Murphy-Hill, E.; Delcambre, L.; and Maier, D.\n\n\n \n\n\n\n Journal of Intelligent Information Systems, 29(1): 7–24. August 2007.\n \n\n\n\n
\n\n\n\n \n \n \"Component-BasedPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{Cushing2007ComponentBased,\n    abstract = {{To solve today's ecological problems, scientists need well documented, validated, and coherent data archives. Historically, however, ecologists have collected and stored data idiosyncratically, making data integration even among close collaborators difficult. Further, effective ecology data warehouses and subsequent data mining require that individual databases be accurately described with metadata against which the data themselves have been validated. Using database technology would make documenting data sets for archiving, integration, and data mining easier, but few ecologists have expertise to use database technology and they cannot afford to hire programmers. In this paper, we identify the benefits that would accrue from ecologists' use of modern information technology and the obstacles that prevent that use. We describe our prototype, the CanopyDataBank, through which we aim to enable individual ecologists in the forest canopy research community to be their own database programmers. The key feature that makes this possible is domain-specific database components, which we call templates. We also show how additional tools that reuse these components, such as for visualization, could provide gains in productivity and motivate the use of new technology. Finally, we suggest ways in which communities might share database components and how components might be used to foster easier data integration to solve new ecological problems.}},\n    address = {Hingham, MA, USA},\n    author = {Cushing, Judith B. and Nadkarni, Nalini and Finch, Michael and Fiala, Anne and Murphy-Hill, Emerson and Delcambre, Lois and Maier, David},\n    citeulike-article-id = {11236861},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/jiis07.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1285774},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1007/s10844-006-0028-6},\n    doi = {10.1007/s10844-006-0028-6},\n    issn = {0925-9902},\n    journal = {Journal of Intelligent Information Systems},\n    keywords = {self},\n    month = aug,\n    number = {1},\n    pages = {7--24},\n    posted-at = {2013-10-16 17:33:59},\n    priority = {2},\n    publisher = {Kluwer Academic Publishers},\n    title = {{Component-Based End-User Database Design for Ecologists}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/jiis07.pdf},\n    volume = {29},\n    year = {2007},\n    howpublished = {1. Journal},\n}\n\n
\n
\n\n\n
\n To solve today's ecological problems, scientists need well documented, validated, and coherent data archives. Historically, however, ecologists have collected and stored data idiosyncratically, making data integration even among close collaborators difficult. Further, effective ecology data warehouses and subsequent data mining require that individual databases be accurately described with metadata against which the data themselves have been validated. Using database technology would make documenting data sets for archiving, integration, and data mining easier, but few ecologists have expertise to use database technology and they cannot afford to hire programmers. In this paper, we identify the benefits that would accrue from ecologists' use of modern information technology and the obstacles that prevent that use. We describe our prototype, the CanopyDataBank, through which we aim to enable individual ecologists in the forest canopy research community to be their own database programmers. The key feature that makes this possible is domain-specific database components, which we call templates. We also show how additional tools that reuse these components, such as for visualization, could provide gains in productivity and motivate the use of new technology. Finally, we suggest ways in which communities might share database components and how components might be used to foster easier data integration to solve new ecological problems.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n\n\n\n
\n
\n\n
\n
\n  \n 2. Conference\n \n \n (14)\n \n \n
\n
\n \n \n
\n
\n  \n 2019\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Investigating the Effects of Gender Bias on GitHub.\n \n\n\n \n Imtiaz, N.; Middleton, J.; Chakraborty, J.; Robson, N.; Bai, G.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 2019 International Conference on Software Engineering, 2019. \n \n\n\n\n
\n\n\n\n \n \n \"InvestigatingPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{47860,\ntitle\t= {Investigating the Effects of Gender Bias on GitHub},\nauthor\t= {Nasif Imtiaz and Justin Middleton and Joymallya Chakraborty and Neill Robson and Gina Bai and Emerson Murphy-Hill},\nyear\t= {2019},\nbooktitle\t= {Proceedings of the 2019 International Conference on Software Engineering},\nhowpublished = {2. Conference},\nurl = {https://people.engr.ncsu.edu/ermurph3/papers/icse19gender.pdf}\n}\n\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Do Developers Learn New Tools On The Toilet?.\n \n\n\n \n Murphy-Hill, E.; Smith, E. K.; Sadowski, C.; Jaspan, C.; Winter, C.; Jorde, M. A.; Dolan, A. K.; Trenk, A.; and Gross, S.\n\n\n \n\n\n\n In Proceedings of the 2019 International Conference on Software Engineering, 2019. \n \n\n\n\n
\n\n\n\n \n \n \"DoPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n  \n \n 4 downloads\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{47861,\ntitle\t= {Do Developers Learn New Tools On The Toilet?},\nauthor\t= {Emerson Murphy-Hill and Edward K. Smith and Caitlin Sadowski and Ciera Jaspan and Collin Winter and Matthew A. Jorde and Andrea Knight Dolan and Andrew Trenk and Steve Gross},\nyear\t= {2019},\nbooktitle\t= {Proceedings of the 2019 International Conference on Software Engineering},\nhowpublished = {2. Conference},\nurl = {https://people.engr.ncsu.edu/ermurph3/papers/icse19toilet.pdf}\n}\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2018\n \n \n (6)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n When Not to Comment: Questions and Tradeoffs with API Documentation for C++ Projects.\n \n\n\n \n Head, A.; Sadowski, C.; Murphy-Hill, E.; and Knight, A.\n\n\n \n\n\n\n In Proceedings of the International Conference of Software Engineering, 2018. \n \n\n\n\n
\n\n\n\n \n \n \"WhenPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{headICSE17,\n    author = {Andrew Head and Caitlin Sadowski and Emerson Murphy-Hill and Andrea Knight},\n    booktitle = {Proceedings of the International Conference of Software Engineering},\n    howpublished = {2. Conference},\n    keywords = {program\\_analysis},\n    title = {When Not to Comment: Questions and Tradeoffs with API Documentation for C++ Projects},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/icse18.pdf},\n    year = {2018}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Advantages and Disadvantages of a Monolithic Repository: A case study at Google.\n \n\n\n \n Jaspan, C.; Jorde, M.; Knight, A.; Sadowski, C.; Smith, E.; Winter, C.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the International Conference of Software Engineering: Software Engineering in Practice Track, 2018. \n \n\n\n\n
\n\n\n\n \n \n \"AdvantagesPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{jaspanICSE17,\n    author = {Ciera Jaspan and Matthew Jorde and Andrea Knight and Caitlin Sadowski and Edward Smith and Colin Winter and Emerson Murphy-Hill},\n    booktitle = {Proceedings of the International Conference of Software Engineering: Software Engineering in Practice Track},\n    howpublished = {2. Conference},\n    keywords = {program\\_analysis},\n    title = {Advantages and Disadvantages of a Monolithic Repository: A case study at Google},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/seip18.pdf},\n    year = {2018}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Which Contributions Predict Whether Developers Are Accepted Into GitHub Teams.\n \n\n\n \n Middleton, J.; Murphy-Hill, E.; Green, D.; Meade, A.; Mayer, R.; White, D.; and McDonald, S.\n\n\n \n\n\n\n In Proceedings of the Conference on Mining Software Repositories, 2018. \n \n\n\n\n
\n\n\n\n \n \n \"WhichPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{msr18,\n    author = {Justin Middleton and Emerson Murphy-Hill and Demetrius Green and Adam Meade and Roger Mayer and David White and Steve McDonald},\n    booktitle = {Proceedings of the Conference on Mining Software Repositories},\n    howpublished = {2. Conference},\n    keywords = {program\\_analysis},\n    title = {Which Contributions Predict Whether Developers Are Accepted Into GitHub Teams},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/msr18.pdf},\n    year = {2018}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Does ACM's Code of Ethics Change Ethical Decision Making in Software Development?.\n \n\n\n \n McNamara, A.; Smith, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Foundations of Software Engineering, New Ideas and Emerging Results, 2018. \n \n\n\n\n
\n\n\n\n \n \n \"DoesPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{McNamara18,\n    author = {Andrew McNamara and Justin Smith and Emerson Murphy-Hill},\n    booktitle = {Foundations of Software Engineering, New Ideas and Emerging Results},\n    doi = {10.1145/3236024.3264833},\n    title = {Does ACM's Code of Ethics Change Ethical Decision Making in Software Development?},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/fse18nier.pdf},\n    year = {2018},\n    howpublished = {2. Conference}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n How Should Compilers Explain Problems to Developers?.\n \n\n\n \n Barik, T.; Ford, D.; Murphy-Hill, E.; and Parnin, C.\n\n\n \n\n\n\n In Foundations of Software Engineering, 2018. \n \n\n\n\n
\n\n\n\n \n \n \"HowPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Barik18,\n    author = {Titus Barik and Denae Ford and Emerson Murphy-Hill and Chris Parnin},\n    booktitle = {Foundations of Software Engineering},\n    doi = {10.1145/3236024.3236040},\n    title = {How Should Compilers Explain Problems to Developers?},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/barik_fse18.pdf},\n    year = {2018},\n    howpublished = {2. Conference}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n No half-measures: A study of manual and tool-assisted end-user programming tasks in Excel.\n \n\n\n \n Pandita, R.; Parnin, C.; Hermans, F.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Visual Languages and Human-Centric Computing, 2018. \n \n\n\n\n
\n\n\n\n \n \n \"NoPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Pandita18,\n    author = {Rahul Pandita and Chris Parnin and Felienne Hermans and Emerson Murphy-Hill},\n    booktitle = {Visual Languages and Human-Centric Computing},\n    title = {No half-measures: A study of manual and tool-assisted end-user programming tasks in Excel},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc18.pdf},\n    year = {2018},\n    howpublished = {2. Conference},\n}\n\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2017\n \n \n (5)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Do Developers Read Compiler Error Messages?.\n \n\n\n \n Barik, T.; Smith, J.; Lubick, K.; Holmes, E.; Feng, J.; Murphy-Hill, E.; and Parnin, C.\n\n\n \n\n\n\n In Proceedings of the International Conference of Software Engineering, 2017. \n \n\n\n\n
\n\n\n\n \n \n \"DoPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{BarikICSE17,\n    author = {Titus Barik and Justin Smith and Kevin Lubick and Elisabeth Holmes and Jing Feng and Emerson Murphy-Hill and Chris Parnin},\n    booktitle = {Proceedings of the International Conference of Software Engineering},\n    howpublished = {2. Conference},\n    keywords = {program\\_analysis},\n    title = {Do Developers Read Compiler Error Messages?},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/icse17.pdf},\n    year = {2017}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Just-in-Time Static Analysis.\n \n\n\n \n Do, L. N. Q.; Ali, K.; Livshits, B.; Bodden, E.; Smith, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the International Symposium on Software Testing and Analysis , 2017. \n \n\n\n\n
\n\n\n\n \n \n \"Just-in-TimePaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{nguyen17,\n    author = {Lisa Nguyen Quang Do and Karim Ali and Benjamin Livshits and Eric Bodden and Justin Smith and Emerson Murphy-Hill},\n    booktitle = {Proceedings of the International Symposium on Software Testing and Analysis },\n    title = {{Just-in-Time Static Analysis}},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/issta17.pdf},\n    year = {2017},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Refactoring-Aware Code Review.\n \n\n\n \n Ge, X.; Sarkar, S.; Witschey, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Visual Languages and Human-Centric Computing, 2017. \n \n\n\n\n
\n\n\n\n \n \n \"Refactoring-AwarePaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{ge17,\n    author = {Xi Ge and Saurabh Sarkar and Jim Witschey and Emerson Murphy-Hill },\n    booktitle = {Visual Languages and Human-Centric Computing},\n    keywords = {program\\_analysis},\n    title = {{Refactoring-Aware Code Review}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc17-refactoring.pdf},\n    year = {2017},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Flower: Navigating Program Flow in the IDE.\n \n\n\n \n Smith, J.; Brown, C.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Visual Languages and Human-Centric Computing, 2017. \n \n\n\n\n
\n\n\n\n \n \n \"Flower:Paper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{smith17,\n    author = {Justin Smith and Chris Brown and Emerson Murphy-Hill},\n    booktitle = {Visual Languages and Human-Centric Computing},\n    keywords = {program\\_analysis, security},\n    title = {Flower: Navigating Program Flow in the {IDE}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc17-navigation.pdf},\n    year = {2017},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n How Software Users Recommend Tools to Each Other.\n \n\n\n \n Brown, C.; Middleton, J.; Sharma, E.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Visual Languages and Human-Centric Computing, 2017. \n \n\n\n\n
\n\n\n\n \n \n \"HowPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{brown17,\n    author = {Chris Brown and Justin Middleton and Esha Sharma and Emerson Murphy-Hill},\n    booktitle = {Visual Languages and Human-Centric Computing},\n    keywords = {discovery},\n    title = {How Software Users Recommend Tools to Each Other},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc17-discovery.pdf},\n    year = {2017},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2016\n \n \n (9)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n A Temporal Analysis of Persuasion Principles in Phishing Emails.\n \n\n\n \n Zielinska, O. A.; Welk, A. K.; Mayhorn, C. B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Annual Meeting of the Human Factors and Ergonomics Society, 2016. \n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Zielinska2016Temporal,\n    author = {Zielinska, Olga A. and Welk, Allaire K. and Mayhorn, Christopher B. and Murphy-Hill, Emerson},\n    booktitle = {Annual Meeting of the Human Factors and Ergonomics Society},\n    citeulike-article-id = {14104541},\n    keywords = {phishing},\n    posted-at = {2016-07-29 23:39:13},\n    priority = {2},\n    title = {A Temporal Analysis of Persuasion Principles in Phishing Emails},\n    year = {2016},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n A Tool for Visualizing Patterns of Spreadsheet Function Combinations.\n \n\n\n \n Middleton, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Working Conference on Software Visualization, 2016. \n \n\n\n\n
\n\n\n\n \n \n \"APaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Middleton2016Tool,\n    author = {Middleton, Justin and Murphy-Hill, Emerson},\n    booktitle = {Working Conference on Software Visualization},\n    citeulike-article-id = {14104519},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/vissoft16.pdf},\n    keywords = {adoption, discovery, spreadsheets},\n    posted-at = {2016-07-29 20:15:14},\n    priority = {2},\n    title = {{A Tool for Visualizing Patterns of Spreadsheet Function Combinations}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vissoft16.pdf},\n    year = {2016},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n A Perspective on Blending Programming Environments and Games: Beyond Points, Badges, and Leaderboards.\n \n\n\n \n Barik, T.; Murphy-Hill, E.; and Zimmermann, T.\n\n\n \n\n\n\n In Visual Languages and Human-Centric Computing, 2016. \n \n\n\n\n
\n\n\n\n \n \n \"APaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Barik2016Perspective,\n    author = {Barik, Titus and Murphy-Hill, Emerson and Zimmermann, Thomas},\n    booktitle = {Visual Languages and Human-Centric Computing},\n    citeulike-article-id = {14104505},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc16-gamification.pdf},\n    keywords = {program\\_analysis},\n    posted-at = {2016-07-29 20:09:23},\n    priority = {2},\n    title = {{A Perspective on Blending Programming Environments and Games: Beyond Points, Badges, and Leaderboards}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc16-gamification.pdf},\n    year = {2016},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Veteran Developers' Contributions and Motivations: An Open Source Perspective.\n \n\n\n \n Morrison, P.; Pandita, R.; Murphy-Hill, E.; and McLaughlin, A.\n\n\n \n\n\n\n In Visual Languages and Human-Centric Computing, 2016. \n \n\n\n\n
\n\n\n\n \n \n \"VeteranPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Morrison2016Veteran,\n    author = {Morrison, Patrick and Pandita, Rahul and Murphy-Hill, Emerson and McLaughlin, Anne},\n    booktitle = {Visual Languages and Human-Centric Computing},\n    citeulike-article-id = {14104499},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc16-veterans.pdf},\n    keywords = {adoption, discovery},\n    posted-at = {2016-07-29 20:02:16},\n    priority = {2},\n    title = {{Veteran Developers' Contributions and Motivations: An Open Source Perspective}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc16-veterans.pdf},\n    year = {2016},\n    howpublished = {2. Conference},\n    keywords = {ageing,discovery},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n From Quick Fixes to Slow Fixes: Reimagining Static Analysis Resolutions to Enable Design Space Exploration.\n \n\n\n \n Barik, T.; Song, Y.; Johnson, B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In International Conference on Software Maintenance and Evolution, 2016. \n \n\n\n\n
\n\n\n\n \n \n \"FromPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Barik2016From,\n    author = {Barik, Titus and Song, Yoonki and Johnson, Brittany and Murphy-Hill, Emerson},\n    booktitle = {International Conference on Software Maintenance and Evolution},\n    citeulike-article-id = {14104203},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/icsme16.pdf},\n    keywords = {program\\_analysis},\n    posted-at = {2016-07-29 19:06:52},\n    priority = {2},\n    title = {{From Quick Fixes to Slow Fixes: Reimagining Static Analysis Resolutions to Enable Design Space Exploration}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icsme16.pdf},\n    year = {2016},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Designing for Dystopia: Software Engineering Research for the Post-Apocalypse.\n \n\n\n \n Barik, T.; Pandita, R.; Middleton, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Foundations of Software Engineering, Visions and Reflections Track, 2016. \n \n\n\n\n
\n\n\n\n \n \n \"DesigningPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Barik2016Designing,\n    author = {Barik, Titus and Pandita, Rahul and Middleton, Justin and Murphy-Hill, Emerson},\n    booktitle = {Foundations of Software Engineering, Visions and Reflections Track},\n    citeulike-article-id = {14104202},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/fse16titus.pdf},\n    keywords = {adoption, discovery},\n    posted-at = {2016-07-29 19:03:19},\n    priority = {2},\n    title = {{Designing for Dystopia: Software Engineering Research for the Post-Apocalypse}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/fse16titus.pdf},\n    year = {2016},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n A Cross-Tool Communication Study on Program Analysis Tool Notifications.\n \n\n\n \n Johnson, B.; Pandita, R.; Smith, J.; Ford, D.; Elder, S.; Murphy-Hill, E.; Heckman, S.; and Sadowski, C.\n\n\n \n\n\n\n In Foundations of Software Engineering, 2016. \n \n\n\n\n
\n\n\n\n \n \n \"APaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Johnson2016CrossTool,\n    author = {Johnson, Brittany and Pandita, Rahul and Smith, Justin and Ford, Denae and Elder, Sarah and Murphy-Hill, Emerson and Heckman, Sarah and Sadowski, Caitlin},\n    booktitle = {Foundations of Software Engineering},\n    citeulike-article-id = {14104200},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/fse16.pdf},\n    keywords = {program\\_analysis, security},\n    posted-at = {2016-07-29 18:55:04},\n    priority = {2},\n    title = {{A Cross-Tool Communication Study on Program Analysis Tool Notifications}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/fse16.pdf},\n    year = {2016},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n The Persuasive Phish: Examining the Social Psychological Principles Hidden in Phishing Emails.\n \n\n\n \n Zielinska, O.; Welk, A.; Mayhorn, C. B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the Symposium and Bootcamp on the Science of Security, of HotSos '16, pages 126, New York, NY, USA, 2016. ACM\n \n\n\n\n
\n\n\n\n \n \n Paper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Zielinska2016Persuasive,\n    abstract = {{Phishing is a social engineering tactic used to trick people into revealing personal information [Zielinska, Tembe, Hong, Ge, Murphy-Hill, \\& Mayhorn 2014]. As phishing emails continue to infiltrate users' mailboxes, what social engineering techniques are the phishers using to successfully persuade victims into releasing sensitive information? Cialdini's [2007] six principles of persuasion (authority, social proof, liking/similarity, commitment/consistency, scarcity, and reciprocation) have been linked to elements of phishing emails [Akbar 2014; Ferreira, \\& Lenzini 2015]; however, the findings have been conflicting. Authority and scarcity were found as the most common persuasion principles in 207 emails obtained from a Netherlands database [Akbar 2014], while liking/similarity was the most common principle in 52 personal emails available in Luxemborg and England [Ferreira et al. 2015]. The purpose of this study was to examine the persuasion principles present in emails available in the United States over a period of five years. Two reviewers assessed eight hundred eighty-seven phishing emails from Arizona State University, Brown University, and Cornell University for Cialdini's six principles of persuasion. Each email was evaluated using a questionnaire adapted from the Ferreira et al. [2015] study. There was an average agreement of 87\\% per item between the two raters. Spearman's Rho correlations were used to compare email characteristics over time. During the five year period under consideration (2010--2015), the persuasion principles of commitment/consistency and scarcity have increased over time, while the principles of reciprocation and social proof have decreased over time. Authority and liking/similarity revealed mixed results with certain characteristics increasing and others decreasing. The commitment/consistency principle could be seen in the increase of emails referring to elements outside the email to look more reliable, such as Google Docs or Adobe Reader (rs(850) = .12, p =.001), while the scarcity principle could be seen in urgent elements that could encourage users to act quickly and may have had success in eliciting a response from users (rs(850) = .09, p =.01). Reciprocation elements, such as a requested reply, decreased over time (rs(850) = -.12, p =.001). Additionally, the social proof principle present in emails by referring to actions performed by other users also decreased (rs(850) = -.10, p =.01). Two persuasion principles exhibited both an increase and decrease in their presence in emails over time: authority and liking/similarity. These principles could increase phishing rate success if used appropriately, but could also raise suspicions in users and decrease compliance if used incorrectly. Specifically, the source of the email, which corresponds to the authority principle, displayed an increase over time in educational institutes (rs(850) = .21, p <.001), but a decrease in financial institutions (rs(850) = -.18, p <.001). Similarly, the liking/similarity principle revealed an increase over time of logos present in emails (rs(850) = .18, p <.001) and decrease in service details, such as payment information (rs(850) = -.16, p <.001). The results from this study offer a different perspective regarding phishing. Previous research has focused on the user aspect; however, few studies have examined the phisher perspective and the social psychological techniques they are implementing. Additionally, they have yet to look at the success of the social psychology techniques. Results from this study can be used to help to predict future trends and inform training programs, as well as machine learning programs used to identify phishing messages.}},\n    address = {New York, NY, USA},\n    author = {Zielinska, Olga and Welk, Allaire and Mayhorn, Christopher B. and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the Symposium and Bootcamp on the Science of Security},\n    citeulike-article-id = {14104185},\n    citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=2898375.2898382},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1145/2898375.2898382},\n    doi = {10.1145/2898375.2898382},\n    isbn = {978-1-4503-4277-3},\n    keywords = {phishing},\n    location = {Pittsburgh, Pennsylvania},\n    pages = {126},\n    posted-at = {2016-07-29 18:23:06},\n    priority = {2},\n    publisher = {ACM},\n    series = {HotSos '16},\n    title = {{The Persuasive Phish: Examining the Social Psychological Principles Hidden in Phishing Emails}},\n    url = {http://dx.doi.org/10.1145/2898375.2898382},\n    year = {2016},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Phishing is a social engineering tactic used to trick people into revealing personal information [Zielinska, Tembe, Hong, Ge, Murphy-Hill, & Mayhorn 2014]. As phishing emails continue to infiltrate users' mailboxes, what social engineering techniques are the phishers using to successfully persuade victims into releasing sensitive information? Cialdini's [2007] six principles of persuasion (authority, social proof, liking/similarity, commitment/consistency, scarcity, and reciprocation) have been linked to elements of phishing emails [Akbar 2014; Ferreira, & Lenzini 2015]; however, the findings have been conflicting. Authority and scarcity were found as the most common persuasion principles in 207 emails obtained from a Netherlands database [Akbar 2014], while liking/similarity was the most common principle in 52 personal emails available in Luxemborg and England [Ferreira et al. 2015]. The purpose of this study was to examine the persuasion principles present in emails available in the United States over a period of five years. Two reviewers assessed eight hundred eighty-seven phishing emails from Arizona State University, Brown University, and Cornell University for Cialdini's six principles of persuasion. Each email was evaluated using a questionnaire adapted from the Ferreira et al. [2015] study. There was an average agreement of 87% per item between the two raters. Spearman's Rho correlations were used to compare email characteristics over time. During the five year period under consideration (2010–2015), the persuasion principles of commitment/consistency and scarcity have increased over time, while the principles of reciprocation and social proof have decreased over time. Authority and liking/similarity revealed mixed results with certain characteristics increasing and others decreasing. The commitment/consistency principle could be seen in the increase of emails referring to elements outside the email to look more reliable, such as Google Docs or Adobe Reader (rs(850) = .12, p =.001), while the scarcity principle could be seen in urgent elements that could encourage users to act quickly and may have had success in eliciting a response from users (rs(850) = .09, p =.01). Reciprocation elements, such as a requested reply, decreased over time (rs(850) = -.12, p =.001). Additionally, the social proof principle present in emails by referring to actions performed by other users also decreased (rs(850) = -.10, p =.01). Two persuasion principles exhibited both an increase and decrease in their presence in emails over time: authority and liking/similarity. These principles could increase phishing rate success if used appropriately, but could also raise suspicions in users and decrease compliance if used incorrectly. Specifically, the source of the email, which corresponds to the authority principle, displayed an increase over time in educational institutes (rs(850) = .21, p <.001), but a decrease in financial institutions (rs(850) = -.18, p <.001). Similarly, the liking/similarity principle revealed an increase over time of logos present in emails (rs(850) = .18, p <.001) and decrease in service details, such as payment information (rs(850) = -.16, p <.001). The results from this study offer a different perspective regarding phishing. Previous research has focused on the user aspect; however, few studies have examined the phisher perspective and the social psychological techniques they are implementing. Additionally, they have yet to look at the success of the social psychology techniques. Results from this study can be used to help to predict future trends and inform training programs, as well as machine learning programs used to identify phishing messages.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Software Security Education at Scale.\n \n\n\n \n Theisen, C.; Williams, L.; Murphy-Hill, E.; and Oliver, K.\n\n\n \n\n\n\n In International Conference on Software Engineering, Software Engineering Education and Training Track, 2016. \n \n\n\n\n
\n\n\n\n \n \n \"SoftwarePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Theisen2016Software,\n    author = {Theisen, Christopher and Williams, Laurie and Murphy-Hill, Emerson and Oliver, Kevin},\n    booktitle = {International Conference on Software Engineering, Software Engineering Education and Training Track},\n    citeulike-article-id = {13991766},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2889160.2889186},\n    doi = {10.1145/2889160.2889186},\n    keywords = {security},\n    posted-at = {2016-03-31 16:49:32},\n    priority = {2},\n    title = {{Software Security Education at Scale}},\n    url = {http://dx.doi.org/10.1145/2889160.2889186},\n    year = {2016},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2015\n \n \n (10)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n A Study of Interactive Code Annotation for Access Control Vulnerabilities.\n \n\n\n \n Thomas, T.; Smith, J.; Murphy-Hill, E.; Chu, B.; and Lipford, H.\n\n\n \n\n\n\n In Proceedings of Visual Languages and Human Centric Computing, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"APaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Thomas2015Study,\n    author = {Thomas, Tyler and Smith, Justin and Murphy-Hill, Emerson and Chu, Bei-Tseng and Lipford, Heather},\n    booktitle = {Proceedings of Visual Languages and Human Centric Computing},\n    citeulike-article-id = {13703567},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/VLHCC.2015.7357200},\n    doi = {10.1109/VLHCC.2015.7357200},\n    keywords = {program\\_analysis, security},\n    posted-at = {2015-08-15 19:08:17},\n    priority = {0},\n    title = {{A Study of Interactive Code Annotation for Access Control Vulnerabilities}},\n    url = {http://dx.doi.org/10.1109/VLHCC.2015.7357200},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Bespoke Tools: Adapted to the Concepts Developers Know.\n \n\n\n \n Johnson, B.; Pandita, R.; Murphy-Hill, E.; and Heckman, S.\n\n\n \n\n\n\n In Proceedings of Foundations of Software Engineering, New and Emerging Results Track, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"BespokePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Johnson2015Bespoke,\n    author = {Johnson, Brittany and Pandita, Rahul and Murphy-Hill, Emerson and Heckman, Sarah},\n    booktitle = {Proceedings of Foundations of Software Engineering, New and Emerging Results Track},\n    citeulike-article-id = {13674458},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2786805.2803197},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/fse15-nier-brittany.pdf},\n    doi = {10.1145/2786805.2803197},\n    keywords = {fse15, program\\_analysis},\n    posted-at = {2015-07-16 12:09:37},\n    priority = {0},\n    title = {{Bespoke Tools: Adapted to the Concepts Developers Know}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/fse15-nier-brittany.pdf},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n I Heart Hacker News: Expanding Qualitative Research Findings by Analyzing Social News Websites.\n \n\n\n \n Barik, T.; Johnson, B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of Foundations of Software Engineering, New and Emerging Results Track, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"IPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Barik2015I,\n    author = {Barik, Titus and Johnson, Brittany and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of Foundations of Software Engineering, New and Emerging Results Track},\n    citeulike-article-id = {13674455},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2786805.2803200},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/fse15-nier-titus.pdf},\n    doi = {10.1145/2786805.2803200},\n    keywords = {discovery, fse15, program\\_analysis},\n    posted-at = {2015-07-16 12:07:04},\n    priority = {0},\n    title = {{I Heart Hacker News: Expanding Qualitative Research Findings by Analyzing Social News Websites}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/fse15-nier-titus.pdf},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Questions Developers Ask While Diagnosing Potential Security Vulnerabilities with Static Analysis.\n \n\n\n \n Smith, J.; Johnson, B.; Murphy-Hill, E.; Chu, B.; and Lipford, H. R.\n\n\n \n\n\n\n In Proceedings of Foundations of Software Engineering, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"QuestionsPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Smith2015Questions,\n    author = {Smith, Justin and Johnson, Brittany and Murphy-Hill, Emerson and Chu, Bill and Lipford, Heather R.},\n    booktitle = {Proceedings of Foundations of Software Engineering},\n    citeulike-article-id = {13674446},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2786805.2786812},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/fse15-main-justin.pdf},\n    doi = {10.1145/2786805.2786812},\n    keywords = {fse15, security},\n    posted-at = {2015-07-16 12:01:45},\n    priority = {0},\n    title = {{Questions Developers Ask While Diagnosing Potential Security Vulnerabilities with Static Analysis}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/fse15-main-justin.pdf},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Quantifying Developers' Adoption of Security Tools.\n \n\n\n \n Witschey, J.; Zielinska, O.; Welk, A.; Murphy-Hill, E.; Mayhorn, C.; and Zimmermann, T.\n\n\n \n\n\n\n In Proceedings of Foundations of Software Engineering, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"QuantifyingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Witschey2015Quantifying,\n    author = {Witschey, Jim and Zielinska, Olga and Welk, Allaire and Murphy-Hill, Emerson and Mayhorn, Chris and Zimmermann, Thomas},\n    booktitle = {Proceedings of Foundations of Software Engineering},\n    citeulike-article-id = {13674443},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2786805.2786816},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/fse15-main-jim.pdf},\n    doi = {10.1145/2786805.2786816},\n    keywords = {fse15, security},\n    posted-at = {2015-07-16 11:58:19},\n    priority = {0},\n    title = {{Quantifying Developers' Adoption of Security Tools}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/fse15-main-jim.pdf},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Exploring Expert and Novice Mental Models of Phishing.\n \n\n\n \n Zielinska, O. A.; Welk, A. K.; Mayhorn, C. B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the Annual Meeting of the Human Factors and Ergonomics Society, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"ExploringPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Zielinska2015Exploring,\n    author = {Zielinska, Olga A. and Welk, Allaire K. and Mayhorn, Christopher B. and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the Annual Meeting of the Human Factors and Ergonomics Society},\n    citeulike-article-id = {13651019},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1177/1541931215591165},\n    doi = {10.1177/1541931215591165},\n    keywords = {phishing},\n    posted-at = {2015-06-18 16:36:51},\n    priority = {2},\n    title = {{Exploring Expert and Novice Mental Models of Phishing}},\n    url = {http://dx.doi.org/10.1177/1541931215591165},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Fuse: A Reproducible, Extendable, Internet-scale Corpus of Spreadsheets.\n \n\n\n \n Barik, T.; Lubick, K.; Smith, J.; Slankas, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 12th Working Conference on Mining Software Repositories, Data Showcase, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"Fuse:Paper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Barik2015Fuse,\n    author = {Barik, Titus and Lubick, Kevin and Smith, Justin and Slankas, John and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the 12th Working Conference on Mining Software Repositories, Data Showcase},\n    citeulike-article-id = {13568453},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/MSR.2015.70},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/icse-msr-15.pdf},\n    doi = {10.1109/MSR.2015.70},\n    keywords = {adoption, discovery, icse2015, spreadsheets, tool\\_adoption},\n    posted-at = {2015-04-02 13:38:49},\n    priority = {2},\n    title = {{Fuse: A Reproducible, Extendable, Internet-scale Corpus of Spreadsheets}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse-msr-15.pdf},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Enron's Spreadsheets and Related Emails: A Dataset and Analysis.\n \n\n\n \n Hermans, F.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the International Conference on Software Engineering, Software Engineering in Practice Track, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"Enron'sPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Hermans2015Enrons,\n    author = {Hermans, Felienne and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the International Conference on Software Engineering, Software Engineering in Practice Track},\n    citeulike-article-id = {13501892},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/ICSE.2015.129},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/icse-seip-15.pdf},\n    doi = {10.1109/ICSE.2015.129},\n    keywords = {adoption, icse2015, nsa, tool\\_adoption, spreadsheets},\n    posted-at = {2015-01-27 02:04:52},\n    priority = {2},\n    title = {Enron's Spreadsheets and Related Emails: A Dataset and Analysis},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse-seip-15.pdf},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Commit Bubbles.\n \n\n\n \n Barik, T.; Lubick, K.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the International Conference on Software Engineering, New Ideas and Emerging Results Track, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"CommitPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Barik2015Commit,\n    author = {Barik, Titus and Lubick, Kevin and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the International Conference on Software Engineering, New Ideas and Emerging Results Track},\n    citeulike-article-id = {13501890},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/ICSE.2015.210},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/icse-nier-15.pdf},\n    doi = {10.1109/ICSE.2015.210},\n    keywords = {icse2015, program\\_analysis},\n    posted-at = {2015-01-27 01:57:56},\n    priority = {2},\n    title = {{Commit Bubbles}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse-nier-15.pdf},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n The Human Factor: a Challenge for Network Reliability Design.\n \n\n\n \n Mushi, M.; Murphy-Hill, E.; and Dutta, R.\n\n\n \n\n\n\n In Proceedings of the International Conference on Design of Reliable Communication Networks, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"ThePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Mushi2015Human,\n    author = {Mushi, Magreth and Murphy-Hill, Emerson and Dutta, Rudra},\n    booktitle = {Proceedings of the International Conference on Design of Reliable Communication Networks},\n    citeulike-article-id = {13501806},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/DRCN.2015.7149000},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/drcn15.pdf},\n    doi = {10.1109/DRCN.2015.7149000},\n    howpublished = {4. Workshop},\n    posted-at = {2015-01-26 22:00:20},\n    priority = {2},\n    title = {{The Human Factor: a Challenge for Network Reliability Design}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/drcn15.pdf},\n    year = {2015},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2014\n \n \n (10)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Speculative Reprogramming.\n \n\n\n \n Palyart, M.; Murphy, G. C.; Murphy-Hill, E.; and Blanc, X.\n\n\n \n\n\n\n In Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering, of FSE 2014, pages 837–840, New York, NY, USA, 2014. ACM\n \n\n\n\n
\n\n\n\n \n \n \"SpeculativePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Palyart2014Speculative,\n    abstract = {{Although software development involves making numerous decisions amongst alternatives, the design and implementation choices made typically become invisible; what a developer sees in the project's artifacts are the end result of all of the decisions. What if, instead, all of the choices made were tracked and it was easy for a developer to revisit a point where a decision was made and choose another alternative? What if the development environment could detect and suggest alternative choices? What if it was easy and low-cost to try another path? We explore the idea of speculative reprogramming that could support a what-if environment for the programming stages of software development.}},\n    address = {New York, NY, USA},\n    author = {Palyart, Marc and Murphy, Gail C. and Murphy-Hill, Emerson and Blanc, Xavier},\n    booktitle = {Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering},\n    citeulike-article-id = {14110662},\n    citeulike-linkout-0 = {http://www.cs.ubc.ca/\\~{}mpalyart/paper/2014\\_FSE\\_SpeculativeReprogramming.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=2666609},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/2635868.2666609},\n    doi = {10.1145/2635868.2666609},\n    isbn = {978-1-4503-3056-5},\n    keywords = {discovery},\n    location = {Hong Kong, China},\n    pages = {837--840},\n    posted-at = {2016-08-10 03:47:48},\n    priority = {2},\n    publisher = {ACM},\n    series = {FSE 2014},\n    title = {{Speculative Reprogramming}},\n    url = {http://www.cs.ubc.ca/\\~{}mpalyart/paper/2014\\_FSE\\_SpeculativeReprogramming.pdf},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Although software development involves making numerous decisions amongst alternatives, the design and implementation choices made typically become invisible; what a developer sees in the project's artifacts are the end result of all of the decisions. What if, instead, all of the choices made were tracked and it was easy for a developer to revisit a point where a decision was made and choose another alternative? What if the development environment could detect and suggest alternative choices? What if it was easy and low-cost to try another path? We explore the idea of speculative reprogramming that could support a what-if environment for the programming stages of software development.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n How Developers Visualize Compiler Messages: A Foundational Approach to Notification Construction.\n \n\n\n \n Barik, T.; Lubick, K.; Christie, S.; and Murphy-Hill, E.\n\n\n \n\n\n\n In 2nd IEEE Working Conference on Software Visualization, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"HowPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Barik2014How,\n    author = {Barik, Titus and Lubick, Kevin and Christie, Samuel and Murphy-Hill, Emerson},\n    booktitle = {2nd IEEE Working Conference on Software Visualization},\n    citeulike-article-id = {13240168},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/VISSOFT.2014.24},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/vissoft14.pdf},\n    doi = {10.1109/VISSOFT.2014.24},\n    keywords = {program\\_analysis, self},\n    posted-at = {2014-06-23 15:12:34},\n    priority = {2},\n    title = {{How Developers Visualize Compiler Messages: A Foundational Approach to Notification Construction}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vissoft14.pdf},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n The Future of Social Learning in Software Engineering.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n Computer, 47(1): 48–54. January 2014.\n \n\n\n\n
\n\n\n\n \n \n \"ThePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@article{MurphyHill2014Future,\n    abstract = {{Building on time-honored strengths of person-to-person social learning, new technologies can help software developers learn from one another more efficiently and productively. In particular, continuous social screencasting is a promising technique for sharing and learning about new software development tools.}},\n    author = {Murphy-Hill, Emerson},\n    citeulike-article-id = {13119857},\n    citeulike-linkout-0 = {http://doi.ieeecomputersociety.org/10.1109/MC.2013.406},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1109/mc.2013.406},\n    day = {01},\n    doi = {10.1109/mc.2013.406},\n    journal = {Computer},\n    keywords = {discovery, self, social\\_networks},\n    month = jan,\n    number = {1},\n    pages = {48--54},\n    posted-at = {2014-03-28 20:54:22},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{The Future of Social Learning in Software Engineering}},\n    url = {http://dx.doi.org/10.1109/mc.2013.406},\n    volume = {47},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Building on time-honored strengths of person-to-person social learning, new technologies can help software developers learn from one another more efficiently and productively. In particular, continuous social screencasting is a promising technique for sharing and learning about new software development tools.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Phishing in International Waters: Exploring Cross-National Differences in Phishing Conceptualizations between Chinese, Indian and American Samples.\n \n\n\n \n Tembe, R.; Zielinska, O.; Liu, Y.; Hong, K. W.; Murphy-Hill, E.; Mayhorn, C.; and Ge, X.\n\n\n \n\n\n\n In Symposium and Bootcamp on the Science of Security, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"PhishingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Tembe2014Phishing,\n    author = {Tembe, Rucha and Zielinska, Olga and Liu, Yuqi and Hong, Kyung W. and Murphy-Hill, Emerson and Mayhorn, Chris and Ge, Xi},\n    booktitle = {Symposium and Bootcamp on the Science of Security},\n    citeulike-article-id = {13119502},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2600176.2600178},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/hotsos14.pdf},\n    doi = {10.1145/2600176.2600178},\n    keywords = {phishing},\n    posted-at = {2014-03-28 19:00:03},\n    priority = {2},\n    title = {{Phishing in International Waters: Exploring Cross-National Differences in Phishing Conceptualizations between Chinese, Indian and American Samples}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/hotsos14.pdf},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Compiler Error Notifications Revisited: An Interaction-First Approach for Helping Developers more Effectively Comprehend and Resolve Error Notifications.\n \n\n\n \n Barik, T.; Witschey, J.; Johnson, B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In International Conference on Software Engineering, New Ideas and Emerging Results, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"CompilerPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Barik2014Compiler,\n    author = {Barik, Titus and Witschey, Jim and Johnson, Brittany and Murphy-Hill, Emerson},\n    booktitle = {International Conference on Software Engineering, New Ideas and Emerging Results},\n    citeulike-article-id = {13110242},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2591062.2591124},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_NIER.pdf},\n    doi = {10.1145/2591062.2591124},\n    keywords = {icse14, program\\_analysis, self},\n    posted-at = {2014-03-18 19:42:09},\n    priority = {2},\n    title = {{Compiler Error Notifications Revisited: An Interaction-First Approach for Helping Developers more Effectively Comprehend and Resolve Error Notifications}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_NIER.pdf},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Experiences Gamifying Developer Adoption of Practices and Tools.\n \n\n\n \n Snipes, W.; Nair, A. R.; and Murphy-Hill, E.\n\n\n \n\n\n\n In International Conference on Software Engineering, Software Engineering in Practice Track, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"ExperiencesPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Snipes2014Experiences,\n    author = {Snipes, Will and Nair, Anil R. and Murphy-Hill, Emerson},\n    booktitle = {International Conference on Software Engineering, Software Engineering in Practice Track},\n    citeulike-article-id = {13110236},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2591062.2591171},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_SEIP.pdf},\n    doi = {10.1145/2591062.2591171},\n    keywords = {adoption, icse14, self},\n    posted-at = {2014-03-18 19:29:33},\n    priority = {2},\n    title = {{Experiences Gamifying Developer Adoption of Practices and Tools}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_SEIP.pdf},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n How Programming Languages Will Co-evolve with Software Engineering: A Bright Decade Ahead.\n \n\n\n \n Murphy-Hill, E.; and Grossman, D.\n\n\n \n\n\n\n In Future of Software Engineering, International Conference on Software Engineering, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"HowPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2014How,\n    author = {Murphy-Hill, Emerson and Grossman, Dan},\n    booktitle = {Future of Software Engineering, International Conference on Software Engineering},\n    citeulike-article-id = {13097815},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2593882.2593898},\n    citeulike-linkout-1 = {https://onedrive.live.com/redir?resid=DD9F9EB62184AD3B!182798\\&\\#38;authkey=!AOX661D4wwC8Vmc\\&\\#38;ithint=file\\%2c.pptx},\n    citeulike-linkout-2 = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_FoSE.pdf},\n    doi = {10.1145/2593882.2593898},\n    keywords = {discovery, icse14, programming\\_languages, self},\n    posted-at = {2014-03-09 22:09:09},\n    priority = {2},\n    title = {{How Programming Languages Will Co-evolve with Software Engineering: A Bright Decade Ahead}},\n    url = {https://onedrive.live.com/redir?resid=DD9F9EB62184AD3B!182798\\&\\#38;authkey=!AOX661D4wwC8Vmc\\&\\#38;ithint=file\\%2c.pptx},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Manual Refactoring Changes with Automated Refactoring Validation.\n \n\n\n \n Ge, X.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the International Conference on Software Engineering, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"ManualPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Ge2014Manual,\n    author = {Ge, Xi and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the International Conference on Software Engineering},\n    citeulike-article-id = {13075926},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2568225.2568280},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_GhostFactor.pdf},\n    doi = {10.1145/2568225.2568280},\n    keywords = {icse14, refactoring, self},\n    posted-at = {2014-03-01 17:48:55},\n    priority = {2},\n    title = {{Manual Refactoring Changes with Automated\nRefactoring Validation}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_GhostFactor.pdf},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Cowboys, Ankle Sprains, and Keepers of Quality: How Is Video Game Development Different from Software Development?.\n \n\n\n \n Murphy-Hill, E.; Zimmermann, T.; and Nagappan, N.\n\n\n \n\n\n\n In Proceedings of the International Conference on Software Engineering, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"Cowboys,Paper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2014Cowboys,\n    author = {Murphy-Hill, Emerson and Zimmermann, Thomas and Nagappan, Nachiappan},\n    booktitle = {Proceedings of the International Conference on Software Engineering},\n    citeulike-article-id = {13075923},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2568225.2568226},\n    citeulike-linkout-1 = {https://onedrive.live.com/redir?resid=DD9F9EB62184AD3B!182709\\&\\#38;authkey=!AOX661D4wwC8Vmc\\&\\#38;ithint=file\\%2c.pptx},\n    citeulike-linkout-2 = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_games.pdf},\n    doi = {10.1145/2568225.2568226},\n    keywords = {icse14, self},\n    posted-at = {2014-03-01 17:45:04},\n    priority = {2},\n    title = {{Cowboys, Ankle Sprains, and Keepers of Quality: How Is Video Game Development Different from Software Development?}},\n    url = {https://onedrive.live.com/redir?resid=DD9F9EB62184AD3B!182709\\&\\#38;authkey=!AOX661D4wwC8Vmc\\&\\#38;ithint=file\\%2c.pptx},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Social Influences on Secure Development Tool Adoption: Why Security Tools Spread.\n \n\n\n \n Xiao, S.; Witschey, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of Computer Supported Cooperative Work, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"SocialPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n  \n \n 2 downloads\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Xiao2014Social,\n    author = {Xiao, Shundan and Witschey, Jim and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of Computer Supported Cooperative Work},\n    citeulike-article-id = {12717103},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2531602.2531722},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/cscw13.pdf},\n    doi = {10.1145/2531602.2531722},\n    keywords = {adoption, nsa, security, self},\n    posted-at = {2013-10-16 15:19:55},\n    priority = {2},\n    title = {{Social Influences on Secure Development Tool Adoption: Why Security Tools Spread}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/cscw13.pdf},\n    year = {2014},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2013\n \n \n (4)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Towards Recognizing and Rewarding Efficient Developer Work Patterns.\n \n\n\n \n Snipes, W.; Augustine, V.; Nair, A. R.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 2013 International Conference on Software Engineering (ICSE), New Ideas and Emerging Results Track (NIER), of ICSE '13, pages 1277–1280, Piscataway, NJ, USA, 2013. IEEE Press\n \n\n\n\n
\n\n\n\n \n \n \"TowardsPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Snipes2013Towards,\n    abstract = {{Software engineering researchers develop great tech- niques consisting of practices and tools that improve efciency and quality of software development. Prior work evaluates developers use of techniques such as Test-Driven-Development and refactoring by measuring actions in the development environ- ment. What we still lack is a method to communicate effectively and motivate developers to adopt best practices and tools. This work proposes a game-like system to motivate adoption while continuously measuring developers use of more efcient development techniques.}},\n    address = {Piscataway, NJ, USA},\n    author = {Snipes, Will and Augustine, Vinay and Nair, Anil R. and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the 2013 International Conference on Software Engineering (ICSE), New Ideas and Emerging Results Track (NIER)},\n    citeulike-article-id = {12613681},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/icse-nier13.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1109/ICSE.2013.6606697},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=2486983},\n    doi = {10.1109/ICSE.2013.6606697},\n    isbn = {978-1-4673-3076-3},\n    keywords = {adoption, self},\n    location = {San Francisco, CA, USA},\n    pages = {1277--1280},\n    posted-at = {2013-10-16 16:58:42},\n    priority = {2},\n    publisher = {IEEE Press},\n    series = {ICSE '13},\n    title = {{Towards Recognizing and Rewarding Efficient Developer Work Patterns}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse-nier13.pdf},\n    year = {2013},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Software engineering researchers develop great tech- niques consisting of practices and tools that improve efciency and quality of software development. Prior work evaluates developers use of techniques such as Test-Driven-Development and refactoring by measuring actions in the development environ- ment. What we still lack is a method to communicate effectively and motivate developers to adopt best practices and tools. This work proposes a game-like system to motivate adoption while continuously measuring developers use of more efcient development techniques.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Why Don't Software Developers Use Static Analysis Tools to Find Bugs?.\n \n\n\n \n Johnson, B.; Song, Y.; Murphy-Hill, E.; and Bowdidge, R.\n\n\n \n\n\n\n In Proceedings of the 2013 International Conference on Software Engineering (ICSE), of ICSE '13, pages 672–681, Piscataway, NJ, USA, 2013. IEEE Press\n \n\n\n\n
\n\n\n\n \n \n \"WhyPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n  \n \n 2 downloads\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Johnson2013Why,\n    abstract = {{Using static analysis tools for automating code inspections can be beneficial for software engineers. Such tools can make finding bugs, or software defects, faster and cheaper than manual inspections. Despite the benefits of using static analysis tools to find bugs, research suggests that these tools are underused. In this paper, we investigate why developers are not widely using static analysis tools and how current tools could potentially be improved. We conducted interviews with 20 developers and found that although all of our participants felt that use is beneficial, false positives and the way in which the warnings are presented, among other things, are barriers to use. We discuss several implications of these results, such as the need for an interactive mechanism to help developers fix defects.}},\n    address = {Piscataway, NJ, USA},\n    author = {Johnson, Brittany and Song, Yoonki and Murphy-Hill, Emerson and Bowdidge, Robert},\n    booktitle = {Proceedings of the 2013 International Conference on Software Engineering (ICSE)},\n    citeulike-article-id = {12716870},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/ICSE.2013.6606613},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/icse13b.pdf},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=2486877},\n    doi = {10.1109/ICSE.2013.6606613},\n    isbn = {978-1-4673-3076-3},\n    keywords = {program\\_analysis, self},\n    location = {San Francisco, CA, USA},\n    pages = {672--681},\n    posted-at = {2013-10-16 16:58:32},\n    priority = {2},\n    publisher = {IEEE Press},\n    series = {ICSE '13},\n    title = {{Why Don't Software Developers Use Static Analysis Tools to Find Bugs?}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse13b.pdf},\n    year = {2013},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Using static analysis tools for automating code inspections can be beneficial for software engineers. Such tools can make finding bugs, or software defects, faster and cheaper than manual inspections. Despite the benefits of using static analysis tools to find bugs, research suggests that these tools are underused. In this paper, we investigate why developers are not widely using static analysis tools and how current tools could potentially be improved. We conducted interviews with 20 developers and found that although all of our participants felt that use is beneficial, false positives and the way in which the warnings are presented, among other things, are barriers to use. We discuss several implications of these results, such as the need for an interactive mechanism to help developers fix defects.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n The Design of Bug Fixes.\n \n\n\n \n Murphy-Hill, E.; Zimmermann, T.; Bird, C.; and Nagappan, N.\n\n\n \n\n\n\n In Proceedings of the 2013 International Conference on Software Engineering (ICSE), of ICSE '13, pages 332–341, Piscataway, NJ, USA, 2013. IEEE Press\n \n\n\n\n
\n\n\n\n \n \n \"ThePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2013Design,\n    abstract = {{When software engineers fix bugs, they may have several options as to how to fix those bugs. Which fix they choose has many implications, both for practitioners and researchers: What is the risk of introducing other bugs during the fix? Is the bug fix in the same code that caused the bug? Is the change fixing the cause or just covering a symptom? In this paper, we investigate alternative fixes to bugs and present an empirical study of how engineers make design choices about how to fix bugs. Based on qualitative interviews with 40 engineers working on a variety of products, data from 6 bug triage meetings, and a survey filled out by 326 engineers, we found a number of factors, many of them non-technical, that influence how bugs are fixed, such as how close to release the software is. We also discuss several implications for research and practice, including ways to make bug prediction and localization more accurate.}},\n    address = {Piscataway, NJ, USA},\n    author = {Murphy-Hill, Emerson and Zimmermann, Thomas and Bird, Christian and Nagappan, Nachiappan},\n    booktitle = {Proceedings of the 2013 International Conference on Software Engineering (ICSE)},\n    citeulike-article-id = {12716874},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/ICSE.2013.6606579},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/icse13a.pdf},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=2486833},\n    doi = {10.1109/ICSE.2013.6606579},\n    isbn = {978-1-4673-3076-3},\n    keywords = {self},\n    location = {San Francisco, CA, USA},\n    pages = {332--341},\n    posted-at = {2013-10-16 16:57:53},\n    priority = {2},\n    publisher = {IEEE Press},\n    series = {ICSE '13},\n    title = {{The Design of Bug Fixes}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse13a.pdf},\n    year = {2013},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n When software engineers fix bugs, they may have several options as to how to fix those bugs. Which fix they choose has many implications, both for practitioners and researchers: What is the risk of introducing other bugs during the fix? Is the bug fix in the same code that caused the bug? Is the change fixing the cause or just covering a symptom? In this paper, we investigate alternative fixes to bugs and present an empirical study of how engineers make design choices about how to fix bugs. Based on qualitative interviews with 40 engineers working on a variety of products, data from 6 bug triage meetings, and a survey filled out by 326 engineers, we found a number of factors, many of them non-technical, that influence how bugs are fixed, such as how close to release the software is. We also discuss several implications for research and practice, including ways to make bug prediction and localization more accurate.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Keeping Up with the Joneses: Assessing Phishing Susceptibility in an Email Task.\n \n\n\n \n Hong, K. W.; Kelley, C. M.; Mayhorn, C. B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the Human Factors and Ergonomics Society Annual Meeting (HFES), 2013. \n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Hong2013Keeping,\n    author = {Hong, Kyung W. and Kelley, Christopher M. and Mayhorn, Christopher B. and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the Human Factors and Ergonomics Society Annual Meeting (HFES)},\n    citeulike-article-id = {12716942},\n    keywords = {nsa, phishing, security, self},\n    posted-at = {2013-10-16 16:57:41},\n    priority = {2},\n    title = {{Keeping Up with the Joneses: Assessing Phishing Susceptibility in an Email Task}},\n    year = {2013},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2012\n \n \n (5)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Continuous social screencasting to facilitate software tool discovery.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n In 2012 34th International Conference on Software Engineering (ICSE), New Ideas and Emerging Results Track (NIER), pages 1317–1320, June 2012. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"ContinuousPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2012Continuous,\n    abstract = {{The wide variety of software development tools available today have a great potential to improve the way developers make software, but that potential goes unfulfilled when developers are not aware of useful tools. In this paper, I introduce the idea of continuous social screencasting, a novel mechanism to help developers gain awareness of relevant tools by enabling them to learn remotely and asychronously from their peers. The idea builds on the strength of several existing techniques that developers already use for discovering new tools, including screencasts and online social networks.}},\n    author = {Murphy-Hill, Emerson},\n    booktitle = {2012 34th International Conference on Software Engineering (ICSE), New Ideas and Emerging Results Track (NIER)},\n    citeulike-article-id = {11237070},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/icseNIER12.pdf},\n    citeulike-linkout-1 = {https://skydrive.live.com/redir?resid=DD9F9EB62184AD3B!363},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1109/icse.2012.6227090},\n    citeulike-linkout-3 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6227090},\n    doi = {10.1109/icse.2012.6227090},\n    institution = {Dept. of Comput. Sci., North Carolina State Univ., Raleigh, NC, USA},\n    isbn = {978-1-4673-1066-6},\n    issn = {0270-5257},\n    keywords = {adoption, discovery, self},\n    month = jun,\n    pages = {1317--1320},\n    posted-at = {2013-10-16 17:29:51},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{Continuous social screencasting to facilitate software tool discovery}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icseNIER12.pdf},\n    year = {2012},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n The wide variety of software development tools available today have a great potential to improve the way developers make software, but that potential goes unfulfilled when developers are not aware of useful tools. In this paper, I introduce the idea of continuous social screencasting, a novel mechanism to help developers gain awareness of relevant tools by enabling them to learn remotely and asychronously from their peers. The idea builds on the strength of several existing techniques that developers already use for discovering new tools, including screencasts and online social networks.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Reconciling manual and automatic refactoring.\n \n\n\n \n Ge, X.; DuBose, Q. L.; and Murphy-Hill, E.\n\n\n \n\n\n\n In 2012 34th International Conference on Software Engineering (ICSE), pages 211–221, June 2012. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"ReconcilingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Ge2012Reconciling,\n    abstract = {{Although useful and widely available, refactoring tools are underused. One cause of this underuse is that a developer sometimes fails to recognize that she is going to refactor before she begins manually refactoring. To address this issue, we conducted a formative study of developers' manual refactoring process, suggesting that developers' reliance on  ” chasing error messages” when manually refactoring is an error-prone manual refactoring strategy. Additionally, our study distilled a set of manual refactoring workflow patterns. Using these patterns, we designed a novel refactoring tool called BeneFactor. BeneFactor detects a developer's manual refactoring, reminds her that automatic refactoring is available, and can complete her refactoring automatically. By alleviating the burden of recognizing manual refactoring, BeneFactor is designed to help solve the refactoring tool underuse problem.}},\n    author = {Ge, Xi and DuBose, Quinton L. and Murphy-Hill, Emerson},\n    booktitle = {2012 34th International Conference on Software Engineering (ICSE)},\n    citeulike-article-id = {11237077},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/icse12.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1109/icse.2012.6227192},\n    citeulike-linkout-2 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6227192},\n    doi = {10.1109/icse.2012.6227192},\n    institution = {Dept. of Comput. Sci., North Carolina State Univ., Raleigh, NC, USA},\n    isbn = {978-1-4673-1066-6},\n    issn = {0270-5257},\n    keywords = {refactoring, self},\n    month = jun,\n    pages = {211--221},\n    posted-at = {2013-10-16 17:29:25},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{Reconciling manual and automatic refactoring}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse12.pdf},\n    year = {2012},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Although useful and widely available, refactoring tools are underused. One cause of this underuse is that a developer sometimes fails to recognize that she is going to refactor before she begins manually refactoring. To address this issue, we conducted a formative study of developers' manual refactoring process, suggesting that developers' reliance on ” chasing error messages” when manually refactoring is an error-prone manual refactoring strategy. Additionally, our study distilled a set of manual refactoring workflow patterns. Using these patterns, we designed a novel refactoring tool called BeneFactor. BeneFactor detects a developer's manual refactoring, reminds her that automatic refactoring is available, and can complete her refactoring automatically. By alleviating the burden of recognizing manual refactoring, BeneFactor is designed to help solve the refactoring tool underuse problem.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Something Smells Phishy: Exploring Definitions, Consequences, and Reactions to Phishing.\n \n\n\n \n Kelley, C. M.; Hong, K. W.; Mayhorn, C. B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In volume 56, pages 2108–2112, September 2012. \n \n\n\n\n
\n\n\n\n \n \n \"SomethingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Kelley2012Something,\n    abstract = {{One hundred fifty-five participants completed a survey on Amazon's Mechanical Turk that assessed characteristics of phishing attacks and requested participants to describe their previous experiences and the related consequences. Results indicated almost all participants had been targets of a phishing with 22\\% reporting these attempts were successful. Participants reported actively engaging in efforts to protect themselves online by noticing the  ” padlock icon” and seeking additional information to verify the legitimacy of e-retailers. Moreover, participants indicated that phishers most frequently pose as members of organizations and that phishing typically occurs via email yet they are aware that other media might also make them susceptible to phishing scams. The reported consequences of phishing attacks go beyond financial loss, with many participants describing social ramifications such as embarrassment and reduced trust. Implications for research in risk communication and design roles by human factors/ergonomics (HF/E) professionals are discussed.}},\n    author = {Kelley, Christopher M. and Hong, Kyung W. and Mayhorn, Christopher B. and Murphy-Hill, Emerson},\n    citeulike-article-id = {12716814},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/hfes12.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1177/1071181312561447},\n    citeulike-linkout-2 = {http://pro.sagepub.com/cgi/content/abstract/56/1/2108},\n    day = {1},\n    doi = {10.1177/1071181312561447},\n    journal = {Proceedings of the Human Factors and Ergonomics Society Annual Meeting (HFES)},\n    keywords = {nsa, phishing, security, self},\n    month = sep,\n    number = {1},\n    pages = {2108--2112},\n    posted-at = {2013-10-16 17:01:51},\n    priority = {2},\n    title = {{Something Smells Phishy: Exploring Definitions, Consequences, and Reactions to Phishing}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/hfes12.pdf},\n    volume = {56},\n    year = {2012},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n One hundred fifty-five participants completed a survey on Amazon's Mechanical Turk that assessed characteristics of phishing attacks and requested participants to describe their previous experiences and the related consequences. Results indicated almost all participants had been targets of a phishing with 22% reporting these attempts were successful. Participants reported actively engaging in efforts to protect themselves online by noticing the ” padlock icon” and seeking additional information to verify the legitimacy of e-retailers. Moreover, participants indicated that phishers most frequently pose as members of organizations and that phishing typically occurs via email yet they are aware that other media might also make them susceptible to phishing scams. The reported consequences of phishing attacks go beyond financial loss, with many participants describing social ramifications such as embarrassment and reduced trust. Implications for research in risk communication and design roles by human factors/ergonomics (HF/E) professionals are discussed.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n An Exploratory Study of Blind Software Developers.\n \n\n\n \n Mealin, S.; and Murphy-Hill, E.\n\n\n \n\n\n\n In 2012 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC), pages 71–74, 2012. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"AnPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Mealin2012Exploratory,\n    author = {Mealin, Sean and Murphy-Hill, Emerson},\n    booktitle = {2012 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)},\n    citeulike-article-id = {12716818},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc12.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1109/vlhcc.2012.6344485},\n    citeulike-linkout-2 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6344485},\n    doi = {10.1109/vlhcc.2012.6344485},\n    institution = {Dept. of Comput. Sci., North Carolina State Univ., Raleigh, NC, USA},\n    isbn = {978-1-4673-0852-6},\n    issn = {1943-6092},\n    keywords = {self},\n    pages = {71--74},\n    posted-at = {2013-10-16 17:01:43},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{An Exploratory Study of Blind Software Developers}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc12.pdf},\n    year = {2012},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Improving Software Developers' Fluency by Recommending Development Environment Commands.\n \n\n\n \n Murphy-Hill, E.; Jiresal, R.; and Murphy, G. C.\n\n\n \n\n\n\n In Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering (FSE), of FSE '12, New York, NY, USA, 2012. ACM\n \n\n\n\n
\n\n\n\n \n \n \"ImprovingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2012Improving,\n    abstract = {{Software developers interact with the development environments they use by issuing commands that execute various programming tools, from source code formatters to build tools. However, developers often only use a small subset of the commands offered by modern development environments, reducing their overall development fluency. In this paper, we use several existing command recommender algorithms to suggest new commands to developers based on their existing command usage history, and also introduce several new algorithms. By running these algorithms on data submitted by several thousand Eclipse users, we describe two studies that explore the feasibility of automatically recommending commands to software developers. The results suggest that, while recommendation is more difficult in development environments than in other domains, it is still feasible to automatically recommend commands to developers based on their usage history, and that using patterns of past discovery is a useful way to do so.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Jiresal, Rahul and Murphy, Gail C.},\n    booktitle = {Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering (FSE)},\n    citeulike-article-id = {12716820},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/fse12.pdf},\n    citeulike-linkout-1 = {https://skydrive.live.com/redir?resid=DD9F9EB62184AD3B!74685},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=2393645},\n    citeulike-linkout-3 = {http://dx.doi.org/10.1145/2393596.2393645},\n    doi = {10.1145/2393596.2393645},\n    isbn = {978-1-4503-1614-9},\n    keywords = {adoption, self},\n    location = {Cary, North Carolina},\n    posted-at = {2013-10-16 17:01:38},\n    priority = {2},\n    publisher = {ACM},\n    series = {FSE '12},\n    title = {{Improving Software Developers' Fluency by Recommending Development Environment Commands}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/fse12.pdf},\n    year = {2012},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Software developers interact with the development environments they use by issuing commands that execute various programming tools, from source code formatters to build tools. However, developers often only use a small subset of the commands offered by modern development environments, reducing their overall development fluency. In this paper, we use several existing command recommender algorithms to suggest new commands to developers based on their existing command usage history, and also introduce several new algorithms. By running these algorithms on data submitted by several thousand Eclipse users, we describe two studies that explore the feasibility of automatically recommending commands to software developers. The results suggest that, while recommendation is more difficult in development environments than in other domains, it is still feasible to automatically recommend commands to developers based on their usage history, and that using patterns of past discovery is a useful way to do so.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2011\n \n \n (4)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Peer Interaction Effectively, Yet Infrequently, Enables Programmers to Discover New Tools.\n \n\n\n \n Murphy-Hill, E.; and Murphy, G. C.\n\n\n \n\n\n\n In Proceedings of the ACM 2011 Conference on Computer Supported Cooperative Work (CSCW), of CSCW '11, pages 405–414, New York, NY, USA, 2011. ACM\n \n\n\n\n
\n\n\n\n \n \n \"PeerPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n  \n \n 2 downloads\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2011Peer,\n    abstract = {{Computer users rely on software tools to work effectively and efficiently, but it is difficult for users to be aware of all the tools that might be useful to them. While there are several potential technical solutions to this difficulty, we know little about social solutions, such as one user telling a peer about a tool. To explore these social solutions in one particular domain, we describe a series of interviews with 18 programmers in industry that explore how tool discovery takes place. These interviews provide a rich set of qualitative data that give us detailed insights into how programmers discover tools. One finding was that, while programmers believe that discovery from peers is effective, they actually discover tools from peers relatively infrequently. Another finding was that programmers can effectively discover tools from their peers both in a co-located and remote settings. We describe several implications of our findings, such as that discovery from peers can be enhanced by improving programmers' ability to communicate openly and concisely about tools.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Murphy, Gail C.},\n    booktitle = {Proceedings of the ACM 2011 Conference on Computer Supported Cooperative Work (CSCW)},\n    citeulike-article-id = {10925814},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/pr203-murphy-hill.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/presentations/CSCW11.pptx},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=1958888},\n    citeulike-linkout-3 = {http://dx.doi.org/10.1145/1958824.1958888},\n    doi = {10.1145/1958824.1958888},\n    isbn = {978-1-4503-0556-3},\n    keywords = {adoption, discovery, self},\n    location = {Hangzhou, China},\n    pages = {405--414},\n    posted-at = {2013-10-16 17:31:21},\n    priority = {2},\n    publisher = {ACM},\n    series = {CSCW '11},\n    title = {{Peer Interaction Effectively, Yet Infrequently, Enables Programmers to Discover New Tools}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/pr203-murphy-hill.pdf},\n    year = {2011},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Computer users rely on software tools to work effectively and efficiently, but it is difficult for users to be aware of all the tools that might be useful to them. While there are several potential technical solutions to this difficulty, we know little about social solutions, such as one user telling a peer about a tool. To explore these social solutions in one particular domain, we describe a series of interviews with 18 programmers in industry that explore how tool discovery takes place. These interviews provide a rich set of qualitative data that give us detailed insights into how programmers discover tools. One finding was that, while programmers believe that discovery from peers is effective, they actually discover tools from peers relatively infrequently. Another finding was that programmers can effectively discover tools from their peers both in a co-located and remote settings. We describe several implications of our findings, such as that discovery from peers can be enhanced by improving programmers' ability to communicate openly and concisely about tools.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Java Generics Adoption: How New Features are Introduced, Championed, or Ignored.\n \n\n\n \n Parnin, C.; Bird, C.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 8th Working Conference on Mining Software Repositories (MSR), of MSR '11, pages 3–12, New York, NY, USA, 2011. ACM\n \n\n\n\n
\n\n\n\n \n \n \"JavaPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Parnin2011Java,\n    abstract = {{Support for generic programming was added to the Java language in 2004, representing perhaps the most significant change to one of the most widely used programming languages today. Researchers and language designers anticipated this addition would relieve many long-standing problems plaguing developers, but surprisingly, no one has yet measured whether generics actually provide such relief. In this paper, we report on the first empirical investigation into how Java generics have been integrated into open source software by automatically mining the history of 20 popular open source Java programs, traversing more than 500 million lines of code in the process. We evaluate five hypotheses, each based on assertions made by prior researchers, about how Java developers use generics. For example, our results suggest that generics do not significantly reduce the number of type casts and that generics are usually adopted by a single champion in a project, rather than all committers.}},\n    address = {New York, NY, USA},\n    author = {Parnin, Chris and Bird, Christian and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the 8th Working Conference on Mining Software Repositories (MSR)},\n    citeulike-article-id = {10863175},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/msr11.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1985441.1985446},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1985441.1985446},\n    doi = {10.1145/1985441.1985446},\n    isbn = {978-1-4503-0574-7},\n    keywords = {programming\\_languages, self},\n    location = {Waikiki, Honolulu, HI, USA},\n    pages = {3--12},\n    posted-at = {2013-10-16 17:30:49},\n    priority = {2},\n    publisher = {ACM},\n    series = {MSR '11},\n    title = {{Java Generics Adoption: How New Features are Introduced, Championed, or Ignored}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/msr11.pdf},\n    year = {2011},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Support for generic programming was added to the Java language in 2004, representing perhaps the most significant change to one of the most widely used programming languages today. Researchers and language designers anticipated this addition would relieve many long-standing problems plaguing developers, but surprisingly, no one has yet measured whether generics actually provide such relief. In this paper, we report on the first empirical investigation into how Java generics have been integrated into open source software by automatically mining the history of 20 popular open source Java programs, traversing more than 500 million lines of code in the process. We evaluate five hypotheses, each based on assertions made by prior researchers, about how Java developers use generics. For example, our results suggest that generics do not significantly reduce the number of type casts and that generics are usually adopted by a single champion in a project, rather than all committers.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Code Hot Spot: A Tool for Extraction and Analysis of Code Change History.\n \n\n\n \n Snipes, W.; Robinson, B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In 2011 27th IEEE International Conference on Software Maintenance (ICSM), pages 392–401, September 2011. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"CodePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Snipes2011Code,\n    abstract = {{Commercial software development teams have limited time available to focus on improvements to their software. These teams need a way to quickly identify areas of the source code that would benefit from improvement, as well as quantifiable data to defend the selected improvements to management. Past research has shown that mining configuration management systems for change information can be useful in determining faulty areas of the code. We present a tool named Code Hot Spot, which mines change records out of Microsoft's TFS configuration management system and creates a report of hot spots. Hot spots are contiguous areas of the code that have higher values of metrics that are indicators of faulty code. We present a study where we use this tool to study projects at ABB to determine areas that need improvement. The resulting data have been used to prioritize areas for additional code reviews and unit testing, as well as identifying change prone areas in need of refactoring.}},\n    author = {Snipes, William and Robinson, Brian and Murphy-Hill, Emerson},\n    booktitle = {2011 27th IEEE International Conference on Software Maintenance (ICSM)},\n    citeulike-article-id = {10676850},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/icsm11.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1109/icsm.2011.6080806},\n    citeulike-linkout-2 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6080806},\n    doi = {10.1109/icsm.2011.6080806},\n    institution = {Ind. Software Syst., ABB Corp. Res., Raleigh, NC, USA},\n    isbn = {978-1-4577-0663-9},\n    issn = {1063-6773},\n    keywords = {self},\n    location = {Williamsburg, VA, USA},\n    month = sep,\n    pages = {392--401},\n    posted-at = {2013-10-16 17:30:39},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{Code Hot Spot: A Tool for Extraction and Analysis of Code Change History}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icsm11.pdf},\n    year = {2011},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Commercial software development teams have limited time available to focus on improvements to their software. These teams need a way to quickly identify areas of the source code that would benefit from improvement, as well as quantifiable data to defend the selected improvements to management. Past research has shown that mining configuration management systems for change information can be useful in determining faulty areas of the code. We present a tool named Code Hot Spot, which mines change records out of Microsoft's TFS configuration management system and creates a report of hot spots. Hot spots are contiguous areas of the code that have higher values of metrics that are indicators of faulty code. We present a study where we use this tool to study projects at ABB to determine areas that need improvement. The resulting data have been used to prioritize areas for additional code reviews and unit testing, as well as identifying change prone areas in need of refactoring.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Restructuring Software with Gestures.\n \n\n\n \n Murphy-Hill, E.; Ayazifar, M.; and Black, A. P.\n\n\n \n\n\n\n In 2011 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC), pages 165–172, 2011. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"RestructuringPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2011Restructuring,\n    author = {Murphy-Hill, Emerson and Ayazifar, Moin and Black, Andrew P.},\n    booktitle = {2011 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)},\n    citeulike-article-id = {12716806},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc11.pdf},\n    citeulike-linkout-1 = {http://skydrive.live.com/redir.aspx?cid=dd9f9eb62184ad3b\\&\\#38;page=view\\&\\#38;resid=DD9F9EB62184AD3B!138\\&\\#38;parid=DD9F9EB62184AD3B!106},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1109/vlhcc.2011.6070394},\n    citeulike-linkout-3 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6070394},\n    doi = {10.1109/vlhcc.2011.6070394},\n    institution = {North Carolina State Univ., Raleigh, NC, USA},\n    isbn = {978-1-4577-1246-3},\n    issn = {1943-6092},\n    keywords = {refactoring, self},\n    pages = {165--172},\n    posted-at = {2013-10-16 17:02:04},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{Restructuring Software with Gestures}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/vlhcc11.pdf},\n    year = {2011},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2010\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n An Interactive Ambient Visualization for Code Smells.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n In Proceedings of the 5th International Symposium on Software Visualization (SOFTVIS), of SOFTVIS '10, pages 5–14, New York, NY, USA, 2010. ACM\n \n\n\n\n
\n\n\n\n \n \n \"AnPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2010Interactive,\n    abstract = {{Code smells are characteristics of software that indicate that code may have a design problem. Code smells have been proposed as a way for programmers to recognize the need for restructuring their software. Because code smells can go unnoticed while programmers are working, tools called smell detectors have been developed to alert programmers to the presence of smells in their code, and to help them understand the cause of those smells. In this paper, we propose a novel smell detector called Stench Blossom that provides an interactive ambient visualization designed to first give programmers a quick, high-level overview of the smells in their code, and then, if they wish, to help in understanding the sources of those code smells. We also describe a laboratory experiment with 12 programmers that tests several hypotheses about our tool. Our findings suggest that programmers can use our tool effectively to identify smells and to make refactoring judgements. This is partly because the tool serves as a memory aid, and partly because it is more reliable and easier to use than heuristics for analyzing smells.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    booktitle = {Proceedings of the 5th International Symposium on Software Visualization (SOFTVIS)},\n    citeulike-article-id = {9559050},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/code\\_smells.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1879216},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1879211.1879216},\n    doi = {10.1145/1879211.1879216},\n    isbn = {978-1-4503-0028-5},\n    keywords = {award\\_distinguished-paper, refactoring, self},\n    location = {Salt Lake City, Utah, USA},\n    pages = {5--14},\n    posted-at = {2013-10-16 17:31:39},\n    priority = {2},\n    publisher = {ACM},\n    series = {SOFTVIS '10},\n    title = {{An Interactive Ambient Visualization for Code Smells}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/code\\_smells.pdf},\n    year = {2010},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Code smells are characteristics of software that indicate that code may have a design problem. Code smells have been proposed as a way for programmers to recognize the need for restructuring their software. Because code smells can go unnoticed while programmers are working, tools called smell detectors have been developed to alert programmers to the presence of smells in their code, and to help them understand the cause of those smells. In this paper, we propose a novel smell detector called Stench Blossom that provides an interactive ambient visualization designed to first give programmers a quick, high-level overview of the smells in their code, and then, if they wish, to help in understanding the sources of those code smells. We also describe a laboratory experiment with 12 programmers that tests several hypotheses about our tool. Our findings suggest that programmers can use our tool effectively to identify smells and to make refactoring judgements. This is partly because the tool serves as a memory aid, and partly because it is more reliable and easier to use than heuristics for analyzing smells.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n A Degree-of-Knowledge Model to Capture Source Code Familiarity.\n \n\n\n \n Fritz, T.; Ou, J.; Murphy, G. C.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering (ICSE), of ICSE '10, pages 385–394, New York, NY, USA, 2010. ACM\n \n\n\n\n
\n\n\n\n \n \n \"APaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Fritz2010DegreeofKnowledge,\n    abstract = {{The size and high rate of change of source code comprising a software system make it difficult for software developers to keep up with who on the team knows about particular parts of the code. Existing approaches to this problem are based solely on authorship of code. In this paper, we present data from two professional software development teams to show that both authorship and interaction information about how a developer interacts with the code are important in characterizing a developer's knowledge of code. We introduce the degree-of-knowledge model that computes automatically a real value for each source code element based on both authorship and interaction information. We show that the degree-of-knowledge model can provide better results than an existing expertise finding approach and also report on case studies of the use of the model to support knowledge transfer and to identify changes of interest.}},\n    address = {New York, NY, USA},\n    author = {Fritz, Thomas and Ou, Jingwen and Murphy, Gail C. and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering (ICSE)},\n    citeulike-article-id = {7262111},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/fritz10.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1806799.1806856},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1806799.1806856},\n    doi = {10.1145/1806799.1806856},\n    isbn = {978-1-60558-719-6},\n    keywords = {award\\_distinguished-paper, self},\n    location = {Cape Town, South Africa},\n    pages = {385--394},\n    posted-at = {2013-10-16 17:02:21},\n    priority = {2},\n    publisher = {ACM},\n    series = {ICSE '10},\n    title = {{A Degree-of-Knowledge Model to Capture Source Code Familiarity}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/fritz10.pdf},\n    year = {2010},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n The size and high rate of change of source code comprising a software system make it difficult for software developers to keep up with who on the team knows about particular parts of the code. Existing approaches to this problem are based solely on authorship of code. In this paper, we present data from two professional software development teams to show that both authorship and interaction information about how a developer interacts with the code are important in characterizing a developer's knowledge of code. We introduce the degree-of-knowledge model that computes automatically a real value for each source code element based on both authorship and interaction information. We show that the degree-of-knowledge model can provide better results than an existing expertise finding approach and also report on case studies of the use of the model to support knowledge transfer and to identify changes of interest.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2009\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n How We Refactor, and How We Know It.\n \n\n\n \n Murphy-Hill, E.; Parnin, C.; and Black, A. P.\n\n\n \n\n\n\n In Proceedings of the 31st International Conference on Software Engineering (ICSE), of ICSE '09, pages 287–297, Washington, DC, USA, 2009. IEEE Computer Society\n \n\n\n\n
\n\n\n\n \n \n \"HowPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2009How,\n    abstract = {{Much of what we know about how programmers refactor in the wild is based on studies that examine just a few software projects. Researchers have rarely taken the time to replicate these studies in other contexts or to examine the assumptions on which they are based. To help put refactoring research on a sound scientific basis, we draw conclusions using four data sets spanning more than 13 000 developers, 240 000 tool-assisted refactorings, 2500 developer hours, and 3400 version control commits. Using these data, we cast doubt on several previously stated assumptions about how programmers refactor, while validating others. For example, we find that programmers frequently do not indicate refactoring activity in commit logs, which contradicts assumptions made by several previous researchers. In contrast, we were able to confirm the assumption that programmers do frequently intersperse refactoring with other program changes. By confirming assumptions and replicating studies made by other researchers, we can have greater confidence that those researchers' conclusions are generalizable.}},\n    address = {Washington, DC, USA},\n    author = {Murphy-Hill, Emerson and Parnin, Chris and Black, Andrew P.},\n    booktitle = {Proceedings of the 31st International Conference on Software Engineering (ICSE)},\n    citeulike-article-id = {5400371},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/icse09.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/presentations/HowWeRefactor.pptx},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=1555044},\n    citeulike-linkout-3 = {http://dx.doi.org/10.1109/icse.2009.5070529},\n    doi = {10.1109/icse.2009.5070529},\n    isbn = {978-1-4244-3453-4},\n    keywords = {award\\_distinguished-paper, refactoring, self},\n    pages = {287--297},\n    posted-at = {2013-10-16 17:34:07},\n    priority = {0},\n    publisher = {IEEE Computer Society},\n    series = {ICSE '09},\n    title = {{How We Refactor, and How We Know It}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse09.pdf},\n    year = {2009},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Much of what we know about how programmers refactor in the wild is based on studies that examine just a few software projects. Researchers have rarely taken the time to replicate these studies in other contexts or to examine the assumptions on which they are based. To help put refactoring research on a sound scientific basis, we draw conclusions using four data sets spanning more than 13 000 developers, 240 000 tool-assisted refactorings, 2500 developer hours, and 3400 version control commits. Using these data, we cast doubt on several previously stated assumptions about how programmers refactor, while validating others. For example, we find that programmers frequently do not indicate refactoring activity in commit logs, which contradicts assumptions made by several previous researchers. In contrast, we were able to confirm the assumption that programmers do frequently intersperse refactoring with other program changes. By confirming assumptions and replicating studies made by other researchers, we can have greater confidence that those researchers' conclusions are generalizable.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2008\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Breaking the Barriers to Successful Refactoring: Observations and Tools for Extract Method.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n In Proceedings of the 30th International Conference on Software Engineering (ICSE), of ICSE '08, pages 421–430, New York, NY, USA, 2008. ACM\n \n\n\n\n
\n\n\n\n \n \n \"BreakingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2008Breaking,\n    abstract = {{Refactoring is the process of changing the structure of code without changing its behavior. Refactoring can be semi-automated with tools, which should make it easier for programmers to refactor quickly and correctly. However, we have observed that many tools do a poor job of communicating errors triggered by the refactoring process and that programmers using them sometimes refactor slowly, conservatively, and incorrectly. In this paper we characterize problems with current refactoring tools, demonstrate three new tools to assist in refactoring, and report on a user study that compares these new tools against existing tools. The results of the study show that speed, accuracy, and user satisfaction can be significantly increased. From the new tools we induce a set of usability recommendations that we hope will help inspire a new generation of programmer-friendly refactoring tools.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    booktitle = {Proceedings of the 30th International Conference on Software Engineering (ICSE)},\n    citeulike-article-id = {9539342},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/icse08.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1368146},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1368088.1368146},\n    doi = {10.1145/1368088.1368146},\n    isbn = {978-1-60558-079-1},\n    keywords = {refactoring, self},\n    location = {Leipzig, Germany},\n    pages = {421--430},\n    posted-at = {2013-10-16 17:33:37},\n    priority = {2},\n    publisher = {ACM},\n    series = {ICSE '08},\n    title = {{Breaking the Barriers to Successful Refactoring: Observations and Tools for Extract Method}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse08.pdf},\n    year = {2008},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n Refactoring is the process of changing the structure of code without changing its behavior. Refactoring can be semi-automated with tools, which should make it easier for programmers to refactor quickly and correctly. However, we have observed that many tools do a poor job of communicating errors triggered by the refactoring process and that programmers using them sometimes refactor slowly, conservatively, and incorrectly. In this paper we characterize problems with current refactoring tools, demonstrate three new tools to assist in refactoring, and report on a user study that compares these new tools against existing tools. The results of the study show that speed, accuracy, and user satisfaction can be significantly increased. From the new tools we induce a set of usability recommendations that we hope will help inspire a new generation of programmer-friendly refactoring tools.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2005\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Removing Duplication From java.io: a Case Study Using Traits.\n \n\n\n \n Murphy-Hill, E.; Quitslund, P. J.; and Black, A. P.\n\n\n \n\n\n\n In Companion to the 20th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), Practitioner Report, pages 282–291, New York, NY, USA, 2005. ACM Press\n \n\n\n\n
\n\n\n\n \n \n \"RemovingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2005Removing,\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Quitslund, Philip J. and Black, Andrew P.},\n    booktitle = {Companion to the 20th Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), Practitioner Report},\n    citeulike-article-id = {471327},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/oopsla05prac.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/presentations/java.io.ppt},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=1094855.1094963},\n    citeulike-linkout-3 = {http://dx.doi.org/10.1145/1094855.1094963},\n    doi = {10.1145/1094855.1094963},\n    isbn = {1595931937},\n    keywords = {self},\n    pages = {282--291},\n    posted-at = {2013-10-16 17:37:46},\n    priority = {0},\n    publisher = {ACM Press},\n    title = {{Removing Duplication From java.io: a Case Study Using Traits}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/oopsla05prac.pdf},\n    year = {2005},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2004\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Traits: Experience with a Language Feature.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n In Companion to the 19th Annual ACM SIGPLAN Conference on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA), Practitioner Report, of OOPSLA '04, pages 275–282, New York, NY, USA, 2004. ACM\n \n\n\n\n
\n\n\n\n \n \n \"Traits:Paper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2004Traits,\n    abstract = {{This paper reports our experiences using traits, collections of pure methods designed to promote reuse and understandability in object-oriented programs. Traits had previously been used to refactor the Smalltalk collection hierarchy, but only by the creators of traits themselves. This experience report represents the first independent test of these language features. Murphy-Hill implemented a substantialmulti-class data structure called ropes that makes significant use of traits. We found that traits improved understandability and reduced the number of methods that needed to be written by 46\\%.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    booktitle = {Companion to the 19th Annual ACM SIGPLAN Conference on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA), Practitioner Report},\n    citeulike-article-id = {471629},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/oopsla04.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1028771},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1028664.1028771},\n    doi = {10.1145/1028664.1028771},\n    isbn = {1-58113-833-4},\n    keywords = {self},\n    location = {Vancouver, BC, CANADA},\n    pages = {275--282},\n    posted-at = {2013-10-16 17:37:55},\n    priority = {0},\n    publisher = {ACM},\n    series = {OOPSLA '04},\n    title = {{Traits: Experience with a Language Feature}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/oopsla04.pdf},\n    year = {2004},\n    howpublished = {2. Conference},\n}\n\n
\n
\n\n\n
\n This paper reports our experiences using traits, collections of pure methods designed to promote reuse and understandability in object-oriented programs. Traits had previously been used to refactor the Smalltalk collection hierarchy, but only by the creators of traits themselves. This experience report represents the first independent test of these language features. Murphy-Hill implemented a substantialmulti-class data structure called ropes that makes significant use of traits. We found that traits improved understandability and reduced the number of methods that needed to be written by 46%.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n\n\n\n
\n
\n\n
\n
\n  \n 3. Book Chapter\n \n \n (2)\n \n \n
\n
\n \n \n
\n
\n  \n 2015\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n .\n \n\n\n \n Snipes, W.; Murphy-Hill, E.; Fritz, T.; Vakilian, M.; Damevski, K.; Nair, A.; and Shepherd, D.\n\n\n \n\n\n\n A Practical Guide to Analyzing IDE Usage Data. 2015.\n \n\n\n\n
\n\n\n\n \n \n \"APaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inbook{Snipes2015Practical,\n    author = {Snipes, Will and Murphy-Hill, Emerson and Fritz, Thomas and Vakilian, Mohsen and Damevski, Kosta and Nair, Anil and Shepherd, David},\n    booktitle = {The Art and Science of Analyzing Software Data},\n    citeulike-article-id = {13679693},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1016/B978-0-12-411519-4.00005-7},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/asd15.pdf},\n    doi = {10.1016/B978-0-12-411519-4.00005-7},\n    keywords = {adoption},\n    posted-at = {2015-07-21 20:39:08},\n    priority = {0},\n    title = {{A Practical Guide to Analyzing IDE Usage Data}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/asd15.pdf},\n    year = {2015},\n    howpublished = {3. Book Chapter},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2014\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n .\n \n\n\n \n Murphy-Hill, E.; and Murphy, G. C.\n\n\n \n\n\n\n Recommendation Delivery: Getting the User Interface Just Right. Robillard, M. P.; Maalej, W.; Walker, R. J.; and Zimmermann, T., editor(s). 2014.\n \n\n\n\n
\n\n\n\n \n \n \"RecommendationPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inbook{MurphyHill2014Recommendation,\n    author = {Murphy-Hill, Emerson and Murphy, Gail C.},\n    booktitle = {Recommendation Systems in Software Engineering},\n    citeulike-article-id = {12717092},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/RSSE\\_Chapter.pdf},\n    editor = {Robillard, Martin P. and Maalej, Walid and Walker, Robert J. and Zimmermann, Thomas},\n    keywords = {adoption, self},\n    posted-at = {2013-10-16 15:20:17},\n    priority = {2},\n    title = {{Recommendation Delivery: Getting the User Interface Just Right}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/RSSE\\_Chapter.pdf},\n    year = {2014},\n    howpublished = {3. Book Chapter},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n\n\n\n
\n
\n\n
\n
\n  \n 4. Workshop\n \n \n (11)\n \n \n
\n
\n \n \n
\n
\n  \n 2018\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Sentiment and Politeness Analysis Tools on Developer Discussions Are Unreliable, but so Are People.\n \n\n\n \n Imtiaz, N.; Middleton, J.; Girouard, P.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the Third International Workshop on Emotion Awareness in Software Engineering, 2018. \n \n\n\n\n
\n\n\n\n \n \n \"SentimentPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{semotion18,\n    author = {Nasif Imtiaz and Justin Middleton and Peter Girouard and Emerson Murphy-Hill},\n    booktitle = {Proceedings of the Third International Workshop on Emotion Awareness in Software Engineering},\n    howpublished = {4. Workshop},\n    keywords = {program\\_analysis},\n    title = {Sentiment and Politeness Analysis Tools on Developer Discussions Are Unreliable, but so Are People},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/semotion18.pdf},\n    year = {2018}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Discovering API Usability Problems at Scale.\n \n\n\n \n Murphy-Hill, E.; Sadowski, C.; Head, A.; Daughtry, J.; Macvean, A.; Jaspan, C.; and Winter, C.\n\n\n \n\n\n\n In Proceedings of the Second International Workshop on API Usage and Evolution, 2018. \n \n\n\n\n
\n\n\n\n \n \n \"DiscoveringPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{wapi18,\n    author = {Emerson Murphy-Hill and Caitlin Sadowski and Andrew Head and John Daughtry and Andrew Macvean and Ciera Jaspan and Collin Winter},\n    booktitle = {Proceedings of the Second International Workshop on API Usage and Evolution},\n    howpublished = {4. Workshop},\n    keywords = {program\\_analysis},\n    title = {Discovering API Usability Problems at Scale},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/wapi18.pdf},\n    year = {2018}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2016\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n What Questions Remain? An Examination of How Developers Understand an Interactive Static Analysis Tool.\n \n\n\n \n Thomas, T. W.; Smith, J.; Lipford, H.; Chu, B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Workshop on Security Information Workers, 2016. \n \n\n\n\n
\n\n\n\n \n \n \"WhatPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Thomas2016What,\n    author = {Thomas, Tyler W. and Smith, Justin and Lipford, Heather and Chu, Bill and Murphy-Hill, Emerson},\n    booktitle = {Workshop on Security Information Workers},\n    citeulike-article-id = {14104198},\n    citeulike-linkout-0 = {https://www.usenix.org/conference/soups2016/workshop-program/wsiw16/presentation/thomas},\n    howpublished = {4. Workshop},\n    keywords = {security},\n    posted-at = {2016-07-29 18:46:40},\n    priority = {2},\n    title = {{What Questions Remain? An Examination of How Developers Understand an Interactive Static Analysis Tool}},\n    url = {https://www.usenix.org/conference/soups2016/workshop-program/wsiw16/presentation/thomas},\n    year = {2016}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Automatic Web Security Unit Testing: XSS Vulnerability Detection.\n \n\n\n \n Mohammadi, M.; Chu, B.; Lipford, H. R.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 11th International Workshop on Automation of Software Test, of AST '16, pages 78–84, New York, NY, USA, 2016. ACM\n \n\n\n\n
\n\n\n\n \n \n \"AutomaticPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Mohammadi2016Automatic,\n    abstract = {{Integrating security testing into the workflow of software developers not only can save resources for separate security testing but also reduce the cost of fixing security vulnerabilities by detecting them early in the development cycle. We present an automatic testing approach to detect a common type of Cross Site Scripting (XSS) vulnerability caused by improper encoding of untrusted data. We automatically extract encoding functions used in a web application to sanitize untrusted inputs and then evaluate their effectiveness by automatically generating XSS attack strings. Our evaluations show that this technique can detect 0-day XSS vulnerabilities that cannot be found by static analysis tools. We will also show that our approach can efficiently cover a common type of XSS vulnerability. This approach can be generalized to test for input validation against other types injections such as command line injection.}},\n    address = {New York, NY, USA},\n    author = {Mohammadi, Mahmoud and Chu, Bill and Lipford, Heather R. and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the 11th International Workshop on Automation of Software Test},\n    citeulike-article-id = {14104186},\n    citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=2896921.2896929},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1145/2896921.2896929},\n    doi = {10.1145/2896921.2896929},\n    howpublished = {4. Workshop},\n    isbn = {978-1-4503-4151-6},\n    keywords = {security},\n    location = {Austin, Texas},\n    pages = {78--84},\n    posted-at = {2016-07-29 18:23:41},\n    priority = {2},\n    publisher = {ACM},\n    series = {AST '16},\n    title = {{Automatic Web Security Unit Testing: XSS Vulnerability Detection}},\n    url = {http://dx.doi.org/10.1145/2896921.2896929},\n    year = {2016}\n}\n\n
\n
\n\n\n
\n Integrating security testing into the workflow of software developers not only can save resources for separate security testing but also reduce the cost of fixing security vulnerabilities by detecting them early in the development cycle. We present an automatic testing approach to detect a common type of Cross Site Scripting (XSS) vulnerability caused by improper encoding of untrusted data. We automatically extract encoding functions used in a web application to sanitize untrusted inputs and then evaluate their effectiveness by automatically generating XSS attack strings. Our evaluations show that this technique can detect 0-day XSS vulnerabilities that cannot be found by static analysis tools. We will also show that our approach can efficiently cover a common type of XSS vulnerability. This approach can be generalized to test for input validation against other types injections such as command line injection.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2015\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Can Social Screencasting Help Developers Learn New Tools?.\n \n\n\n \n Lubick, K.; Barik, T.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 8th International Workshop on Cooperative and Human Aspects of Software Engineering, 2015. \n \n\n\n\n
\n\n\n\n \n \n \"CanPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Lubick2015Can,\n    author = {Lubick, Kevin and Barik, Titus and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the 8th International Workshop on Cooperative and Human Aspects of Software Engineering},\n    citeulike-article-id = {13568449},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/CHASE.2015.18},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/icse-chase-15.pdf},\n    doi = {10.1109/CHASE.2015.18},\n    howpublished = {4. Workshop},\n    keywords = {adoption, discovery, icse2015, tool\\_adoption},\n    posted-at = {2015-04-02 13:31:25},\n    priority = {2},\n    title = {{Can Social Screencasting Help Developers Learn New Tools?}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/icse-chase-15.pdf},\n    year = {2015},\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2014\n \n \n (4)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Designing Interventions to Persuade Software Developers to Adopt Security Tools.\n \n\n\n \n Jordan, B.; Johnson, B.; Witschey, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the CCS Workshop on Security Information Workers, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"DesigningPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Jordan2014Designing,\n    author = {Jordan, Brooke and Johnson, Brittany and Witschey, Jim and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the CCS Workshop on Security Information Workers},\n    citeulike-article-id = {13366838},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2663887.2663900},\n    doi = {10.1145/2663887.2663900},\n    howpublished = {4. Workshop},\n    keywords = {adoption, security, tool\\_adoption},\n    posted-at = {2014-09-18 14:39:30},\n    priority = {2},\n    title = {{Designing Interventions to Persuade Software Developers to Adopt\nSecurity Tools}},\n    url = {http://dx.doi.org/10.1145/2663887.2663900},\n    year = {2014}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Technical and Personal Factors Influencing Developers' Adoption of Security Tools.\n \n\n\n \n Witschey, J.; Xiao, S.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the CCS Workshop on Security Information Workers, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"TechnicalPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Witschey2014Technical,\n    author = {Witschey, Jim and Xiao, Shundan and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the CCS Workshop on Security Information Workers},\n    citeulike-article-id = {13366827},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2663887.2663898},\n    doi = {10.1145/2663887.2663898},\n    howpublished = {4. Workshop},\n    keywords = {adoption, security, tool\\_adoption},\n    posted-at = {2014-09-18 14:36:46},\n    priority = {2},\n    title = {{Technical and Personal Factors Influencing Developers' Adoption of Security Tools}},\n    url = {http://dx.doi.org/10.1145/2663887.2663898},\n    year = {2014}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Interactive Code Annotation for Security Vulnerability Detection.\n \n\n\n \n Lipford, H.; Thomas, T.; Chu, B.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the CCS Workshop on Security Information Workers, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"InteractivePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Lipford2014Interactive,\n    author = {Lipford, Heather and Thomas, Tyler and Chu, Bill and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the CCS Workshop on Security Information Workers},\n    citeulike-article-id = {13366816},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2663887.2663901},\n    doi = {10.1145/2663887.2663901},\n    howpublished = {4. Workshop},\n    keywords = {security},\n    posted-at = {2014-09-18 14:31:00},\n    priority = {2},\n    title = {{Interactive Code Annotation for Security Vulnerability Detection}},\n    url = {http://dx.doi.org/10.1145/2663887.2663901},\n    year = {2014}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Towards Refactoring-Aware Code Review.\n \n\n\n \n Ge, X.; Sarkar, S.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Computer-Human Aspects of Software Engineering (CHASE), at the International Conference on Software Engineering, 2014. \n \n\n\n\n
\n\n\n\n \n \n \"TowardsPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Ge2014Towards,\n    author = {Ge, Xi and Sarkar, Saurabh and Murphy-Hill, Emerson},\n    booktitle = {Computer-Human Aspects of Software Engineering (CHASE), at the International Conference on Software Engineering},\n    citeulike-article-id = {13104986},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2593702.2593706},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_CHASE.pdf},\n    doi = {10.1145/2593702.2593706},\n    howpublished = {4. Workshop},\n    keywords = {icse14, refactoring, self},\n    posted-at = {2014-03-12 18:29:44},\n    priority = {2},\n    title = {{Towards Refactoring-Aware Code Review}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/ICSE14\\_CHASE.pdf},\n    year = {2014}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2013\n \n \n (4)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Conducting Interview Studies: Challenges, Lessons Learned, and Open Questions.\n \n\n\n \n Witschey, J.; Murphy-Hill, E.; and Xiao, S.\n\n\n \n\n\n\n In 2013 1st International Workshop on Conducting Empirical Studies in Industry (CESI), pages 51–54, May 2013. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"ConductingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Witschey2013Conducting,\n    author = {Witschey, Jim and Murphy-Hill, Emerson and Xiao, Shundan},\n    booktitle = {2013 1st International Workshop on Conducting Empirical Studies in Industry (CESI)},\n    citeulike-article-id = {12716841},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/cesi13.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1109/cesi.2013.6618471},\n    citeulike-linkout-2 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6618471},\n    doi = {10.1109/cesi.2013.6618471},\n    howpublished = {4. Workshop},\n    institution = {Dept. of Comput. Sci., North Carolina State Univ., Raleigh, NC, USA},\n    keywords = {adoption, nsa, security, self},\n    month = may,\n    pages = {51--54},\n    posted-at = {2013-10-16 16:59:54},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{Conducting Interview Studies: Challenges, Lessons Learned, and Open Questions}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/cesi13.pdf},\n    year = {2013}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Live Feedback on Behavioral Changes.\n \n\n\n \n Soares, G.; Murphy-Hill, E.; and Gheyi, R.\n\n\n \n\n\n\n In 2013 1st International Workshop on Live Programming (LIVE), pages 23–26, May 2013. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"LivePaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Soares2013Live,\n    author = {Soares, Gustavo and Murphy-Hill, Emerson and Gheyi, Rohit},\n    booktitle = {2013 1st International Workshop on Live Programming (LIVE)},\n    citeulike-article-id = {12716850},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/live13.pdf},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1109/live.2013.6617344},\n    citeulike-linkout-2 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6617344},\n    doi = {10.1109/live.2013.6617344},\n    howpublished = {4. Workshop},\n    institution = {Department of Computing Systems, Federal University of Campina Grande, Brazil},\n    keywords = {self},\n    month = may,\n    pages = {23--26},\n    posted-at = {2013-10-16 16:59:13},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{Live Feedback on Behavioral Changes}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/live13.pdf},\n    year = {2013}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Is Programming Knowledge Related to Age? an Exploration of Stack Overflow.\n \n\n\n \n Morrison, P.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 10th Working Conference on Mining Software Repositories (MSR), Challenge Track, of MSR '13, pages 69–72, Piscataway, NJ, USA, 2013. IEEE Press\n \n\n\n\n
\n\n\n\n \n \n \"IsPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Morrison2013Programming,\n    abstract = {{Becoming an expert at programming is thought to take an estimated 10,000 hours of deliberate practice . But what happens after that? Do programming experts continue to develop, do they plateau, or is there a decline at some point? A diversity of opinion exists on this matter, but many seem to think that aging brings a decline in adoption and absorption of new programming knowledge. We develop several research questions on this theme, and draw on data from StackOverflow to address these questions. The goal of this research is to support career planning and staff development for programmers by identifying age-related trends in StackOverflow data. We observe that programmer reputation scores increase relative to age well into the 50's, that programmers in their 30's tend to focus on fewer areas relative to those younger or older in age, and that there is not a strong correlation between age and scores in specific knowledge areas.}},\n    address = {Piscataway, NJ, USA},\n    author = {Morrison, Patrick and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the 10th Working Conference on Mining Software Repositories (MSR), Challenge Track},\n    citeulike-article-id = {12716856},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/MSR.2013.6624008},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/msr13.pdf},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=2487102},\n    doi = {10.1109/MSR.2013.6624008},\n    howpublished = {4. Workshop},\n    isbn = {978-1-4673-2936-1},\n    keywords = {ageing, self},\n    location = {San Francisco, CA, USA},\n    pages = {69--72},\n    posted-at = {2013-10-16 16:59:03},\n    priority = {2},\n    publisher = {IEEE Press},\n    series = {MSR '13},\n    title = {{Is Programming Knowledge Related to Age? an Exploration of Stack Overflow}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/msr13.pdf},\n    year = {2013}\n}\n\n
\n
\n\n\n
\n Becoming an expert at programming is thought to take an estimated 10,000 hours of deliberate practice . But what happens after that? Do programming experts continue to develop, do they plateau, or is there a decline at some point? A diversity of opinion exists on this matter, but many seem to think that aging brings a decline in adoption and absorption of new programming knowledge. We develop several research questions on this theme, and draw on data from StackOverflow to address these questions. The goal of this research is to support career planning and staff development for programmers by identifying age-related trends in StackOverflow data. We observe that programmer reputation scores increase relative to age well into the 50's, that programmers in their 30's tend to focus on fewer areas relative to those younger or older in age, and that there is not a strong correlation between age and scores in specific knowledge areas.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Improving developer participation rates in surveys.\n \n\n\n \n Smith, E.; Loftin, R.; Murphy-Hill, E.; Bird, C.; and Zimmermann, T.\n\n\n \n\n\n\n In 2013 6th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE), pages 89–92, May 2013. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"ImprovingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Smith2013Improving,\n    author = {Smith, Edward and Loftin, Robert and Murphy-Hill, Emerson and Bird, Christian and Zimmermann, Thomas},\n    booktitle = {2013 6th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)},\n    citeulike-article-id = {12716860},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/chase13.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/papers/chase13.pdf},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1109/chase.2013.6614738},\n    citeulike-linkout-3 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6614738},\n    doi = {10.1109/chase.2013.6614738},\n    howpublished = {4. Workshop},\n    institution = {Comput. Sci., Univ. of Maryland, College Park, MD, USA},\n    keywords = {self},\n    month = may,\n    pages = {89--92},\n    posted-at = {2013-10-16 16:58:54},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{Improving developer participation rates in surveys}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/chase13.pdf},\n    year = {2013}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2012\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n How can research about software developers generalize?.\n \n\n\n \n Murphy-Hill, E.; and Williams, L.\n\n\n \n\n\n\n In 2012 5th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE), pages 105–109, June 2012. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"HowPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2012How,\n    abstract = {{Research that studies software developers can have a larger impact when its results generalize to other contexts. However, it is often unclear if, how, and why such results generalize. In this position paper, we aim to motivate software engineering researchers to generalize their findings. To meet this aim, we firstly enumerate the dimensions in which software engineering generalizations are made, and secondly, propose several practical ways researchers can make their work more generalizable. In meeting our aim, we hope to help the software engineering research community maximize their impact outside of software engineering.}},\n    author = {Murphy-Hill, Emerson and Williams, Laurie},\n    booktitle = {2012 5th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)},\n    citeulike-article-id = {11237066},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/chase12.pdf},\n    citeulike-linkout-1 = {https://skydrive.live.com/redir?resid=DD9F9EB62184AD3B!345},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1109/chase.2012.6223002},\n    citeulike-linkout-3 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6223002},\n    doi = {10.1109/chase.2012.6223002},\n    howpublished = {4. Workshop},\n    institution = {Dept. of Comput. Sci., North Carolina State Univ., Raleigh, NC, USA},\n    isbn = {978-1-4673-1823-5},\n    keywords = {self},\n    month = jun,\n    pages = {105--109},\n    posted-at = {2013-10-16 17:29:59},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{How can research about software developers generalize?}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/chase12.pdf},\n    year = {2012}\n}\n\n
\n
\n\n\n
\n Research that studies software developers can have a larger impact when its results generalize to other contexts. However, it is often unclear if, how, and why such results generalize. In this position paper, we aim to motivate software engineering researchers to generalize their findings. To meet this aim, we firstly enumerate the dimensions in which software engineering generalizations are made, and secondly, propose several practical ways researchers can make their work more generalizable. In meeting our aim, we hope to help the software engineering research community maximize their impact outside of software engineering.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2010\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n What is Trust in a Recommender for Software Development?.\n \n\n\n \n Murphy, G. C.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering (RSSE), of RSSE '10, pages 57–58, New York, NY, USA, 2010. ACM\n \n\n\n\n
\n\n\n\n \n \n \"WhatPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Murphy2010What,\n    abstract = {{Many recommendation systems have been built to aid software developers. Few have been evaluated using human-based evaluation strategies. In studying situations where recommendation systems have been used or might be used, we have observed that issues related to trust are important to a developer's acceptance of recommendations. In this position paper, we outline the trust issues that we have identified and suggest some mechanisms for promoting trust in recommendation systems aimed at software developers.}},\n    address = {New York, NY, USA},\n    author = {Murphy, Gail C. and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering (RSSE)},\n    citeulike-article-id = {9973480},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/rsse10.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/presentations/ICSE2010-RSSE-Trust.pptx},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=1808934},\n    citeulike-linkout-3 = {http://dx.doi.org/10.1145/1808920.1808934},\n    doi = {10.1145/1808920.1808934},\n    howpublished = {4. Workshop},\n    isbn = {978-1-60558-974-9},\n    keywords = {adoption, discovery, rsse, rsse\\_proceedings, self},\n    location = {Cape Town, South Africa},\n    pages = {57--58},\n    posted-at = {2013-10-16 17:32:10},\n    priority = {2},\n    publisher = {ACM},\n    series = {RSSE '10},\n    title = {{What is Trust in a Recommender for Software Development?}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/rsse10.pdf},\n    year = {2010}\n}\n\n
\n
\n\n\n
\n Many recommendation systems have been built to aid software developers. Few have been evaluated using human-based evaluation strategies. In studying situations where recommendation systems have been used or might be used, we have observed that issues related to trust are important to a developer's acceptance of recommendations. In this position paper, we outline the trust issues that we have identified and suggest some mechanisms for promoting trust in recommendation systems aimed at software developers.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Understanding Context: Creating a Lasting Impact in Experimental Software Engineering Research.\n \n\n\n \n Murphy-Hill, E.; Murphy, G. C.; and Griswold, W. G.\n\n\n \n\n\n\n In Proceedings of the FSE/SDP Workshop on Future of Software Engineering Research, of FoSER '10, pages 255–258, New York, NY, USA, 2010. ACM\n \n\n\n\n
\n\n\n\n \n \n \"UnderstandingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2010Understanding,\n    abstract = {{Software is developed for and in a vast number of contexts. Some software systems are small in size; some large. Some systems are developed by small teams; some large. Some projects are sensitive to schedule, others to safety of the users. In this position paper, we argue that to make a lasting impact with the software engineering research we conduct, we must understand, make explicit, and vary the context in which our conclusions are drawn. Moreover, we need a better understanding of how research results can be translated or generalized to other contexts, as it is not economically feasible to replicate results across all contexts. We argue that a successful solution to this problem will allow researchers to conduct research within particular contexts, richly characterize those contexts in their writings, and allow other researchers to predictably build on those in differing contexts.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Murphy, Gail C. and Griswold, William G.},\n    booktitle = {Proceedings of the FSE/SDP Workshop on Future of Software Engineering Research},\n    citeulike-article-id = {12716799},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/foser064.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1882362.1882415},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1882362.1882415},\n    doi = {10.1145/1882362.1882415},\n    howpublished = {4. Workshop},\n    isbn = {978-1-4503-0427-6},\n    keywords = {self},\n    location = {Santa Fe, New Mexico, USA},\n    pages = {255--258},\n    posted-at = {2013-10-16 17:02:17},\n    priority = {2},\n    publisher = {ACM},\n    series = {FoSER '10},\n    title = {{Understanding Context: Creating a Lasting Impact in Experimental Software Engineering Research}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/foser064.pdf},\n    year = {2010}\n}\n\n
\n
\n\n\n
\n Software is developed for and in a vast number of contexts. Some software systems are small in size; some large. Some systems are developed by small teams; some large. Some projects are sensitive to schedule, others to safety of the users. In this position paper, we argue that to make a lasting impact with the software engineering research we conduct, we must understand, make explicit, and vary the context in which our conclusions are drawn. Moreover, we need a better understanding of how research results can be translated or generalized to other contexts, as it is not economically feasible to replicate results across all contexts. We argue that a successful solution to this problem will allow researchers to conduct research within particular contexts, richly characterize those contexts in their writings, and allow other researchers to predictably build on those in differing contexts.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2009\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n A Model of Refactoring Tool Use.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the 3rd Workshop on Refactoring Tools (WRT), 2009. \n \n\n\n\n
\n\n\n\n \n \n \"APaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2009Model,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the 3rd Workshop on Refactoring Tools (WRT)},\n    citeulike-article-id = {11236999},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/wrt09.pdf},\n    howpublished = {4. Workshop},\n    keywords = {refactoring, self},\n    posted-at = {2013-10-16 17:32:23},\n    priority = {2},\n    title = {{A Model of Refactoring Tool Use}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/wrt09.pdf},\n    year = {2009}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2008\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Gathering Refactoring Data: a Comparison of Four Methods.\n \n\n\n \n Murphy-Hill, E.; Black, A. P.; Dig, D.; and Parnin, C.\n\n\n \n\n\n\n In Proceedings of the 2nd Workshop on Refactoring Tools (WRT), of WRT '08, New York, NY, USA, 2008. ACM\n \n\n\n\n
\n\n\n\n \n \n \"GatheringPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2008Gathering,\n    abstract = {{Those of us who seek to build better refactoring tools need empirical data collected from real refactoring sessions. The literature reports on different methods for capturing this data, but little is known about how the method of data capture affects the quality of the results. This paper describes 4 methods for drawing conclusions about how programmers refactor, characterizes the assumptions made by each, and presents a family of experiments to test those assumptions. We hope that the results of the experiments will help future researchers choose a data-collection method appropriate to the question that they want to investigate.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Black, Andrew P. and Dig, Danny and Parnin, Chris},\n    booktitle = {Proceedings of the 2nd Workshop on Refactoring Tools (WRT)},\n    citeulike-article-id = {11236967},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/wrt08.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1636649},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1636642.1636649},\n    doi = {10.1145/1636642.1636649},\n    howpublished = {4. Workshop},\n    isbn = {978-1-60558-339-6},\n    keywords = {refactoring, self},\n    location = {Nashville, Tennessee},\n    posted-at = {2013-10-16 17:33:10},\n    priority = {2},\n    publisher = {ACM},\n    series = {WRT '08},\n    title = {{Gathering Refactoring Data: a Comparison of Four Methods}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/wrt08.pdf},\n    year = {2008}\n}\n\n
\n
\n\n\n
\n Those of us who seek to build better refactoring tools need empirical data collected from real refactoring sessions. The literature reports on different methods for capturing this data, but little is known about how the method of data capture affects the quality of the results. This paper describes 4 methods for drawing conclusions about how programmers refactor, characterizes the assumptions made by each, and presents a family of experiments to test those assumptions. We hope that the results of the experiments will help future researchers choose a data-collection method appropriate to the question that they want to investigate.\n
\n\n\n
\n\n\n
\n \n\n \n \n \n\n Seven Habits of a Highly Effective Smell Detector.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n In Proceedings of the 2008 International Workshop on Recommendation Systems for Software Engineering (RSSE), of RSSE '08, pages 36–40, New York, NY, USA, 2008. ACM\n \n\n\n\n
\n\n\n\n \n \n \"SevenPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2008Seven,\n    abstract = {{The process of refactoring code---changing its structure while preserving its meaning---has been identified as an important way of maintaining code quality over time. However, it is sometimes difficult for progammers to identify which pieces of code are in need of refactoring. "Smell detectors" are designed to help programmers in this task, but most smell detectors do not mesh well with "floss refactoring," the recommended tactic in which refactoring and programming are finely interleaved. In this paper we present a smell detector that we have built with floss refactoring in mind by combining seven habits that we postulate are important to consider when designing usable smell detectors. We hope that this combination can help the designers of future smell detectors build tools that align with the way that programmers refactor.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    booktitle = {Proceedings of the 2008 International Workshop on Recommendation Systems for Software Engineering (RSSE)},\n    citeulike-article-id = {8345115},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/rsse08.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1454261},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1454247.1454261},\n    doi = {10.1145/1454247.1454261},\n    howpublished = {4. Workshop},\n    isbn = {978-1-60558-228-3},\n    keywords = {refactoring, rsse, rsse\\_proceedings, self},\n    location = {Atlanta, Georgia},\n    pages = {36--40},\n    posted-at = {2013-10-16 17:32:39},\n    priority = {2},\n    publisher = {ACM},\n    series = {RSSE '08},\n    title = {{Seven Habits of a Highly Effective Smell Detector}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/rsse08.pdf},\n    year = {2008}\n}\n\n
\n
\n\n\n
\n The process of refactoring code—changing its structure while preserving its meaning—has been identified as an important way of maintaining code quality over time. However, it is sometimes difficult for progammers to identify which pieces of code are in need of refactoring. \"Smell detectors\" are designed to help programmers in this task, but most smell detectors do not mesh well with \"floss refactoring,\" the recommended tactic in which refactoring and programming are finely interleaved. In this paper we present a smell detector that we have built with floss refactoring in mind by combining seven habits that we postulate are important to consider when designing usable smell detectors. We hope that this combination can help the designers of future smell detectors build tools that align with the way that programmers refactor.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2007\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Why Don't People Use Refactoring Tools?.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n In Dig, D.; Johnson, R.; Tip, F.; De Moor, O.; and Becicka, J., editor(s), Proceedings of the 1st Workshop on Refactoring Tools (WRT), 2007. TU Berlin Technical Report\n \n\n\n\n
\n\n\n\n \n \n \"WhyPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2007Why,\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    booktitle = {Proceedings of the 1st Workshop on Refactoring Tools (WRT)},\n    citeulike-article-id = {11236898},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/wrt07.pdf},\n    editor = {Dig, Danny and Johnson, Ralph and Tip, Frank and De Moor, Oege and Becicka, Jan},\n    howpublished = {4. Workshop},\n    isbn = {1436-9915},\n    keywords = {refactoring, self},\n    posted-at = {2013-10-16 17:33:55},\n    priority = {2},\n    publisher = {TU Berlin Technical Report},\n    title = {{Why Don't People Use Refactoring Tools?}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/wrt07.pdf},\n    year = {2007}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n High Velocity Refactorings in Eclipse.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n In Proceedings of the 2007 OOPSLA Workshop on Eclipse Technology eXchange (ETX), of ETX 07, pages 1–5, New York, NY, USA, 2007. ACM\n \n\n\n\n
\n\n\n\n \n \n \"HighPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2007High,\n    abstract = {{In Eclipse, and in most other development environments, refactorings are activated by selecting code, then using a menu or hotkey, and finally engaging in a dialog with a "wizard". However, selection is error-prone, menus are slow, hotkeys are hard to remember, and wizards are time-consuming. The problem is that as a consequence, refactoring tools disrupt the programmer's workflow and are perceived to be slower than refactoring by hand. In this paper we present two new user interfaces to Eclipse's existing refactoring engine: marking menus and refactoring cues. Both are designed to increase programming velocity by keeping the tool out of the programmer's way.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    booktitle = {Proceedings of the 2007 OOPSLA Workshop on Eclipse Technology eXchange (ETX)},\n    citeulike-article-id = {11236915},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/etx07.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/presentations/etx07.ppt},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=1328280},\n    citeulike-linkout-3 = {http://dx.doi.org/10.1145/1328279.1328280},\n    doi = {10.1145/1328279.1328280},\n    howpublished = {4. Workshop},\n    isbn = {978-1-60558-015-9},\n    keywords = {refactoring, self},\n    location = {Montreal, Quebec, Canada},\n    pages = {1--5},\n    posted-at = {2013-10-16 17:33:46},\n    priority = {2},\n    publisher = {ACM},\n    series = {ETX 07},\n    title = {{High Velocity Refactorings in Eclipse}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/etx07.pdf},\n    year = {2007}\n}\n\n
\n
\n\n\n
\n In Eclipse, and in most other development environments, refactorings are activated by selecting code, then using a menu or hotkey, and finally engaging in a dialog with a \"wizard\". However, selection is error-prone, menus are slow, hotkeys are hard to remember, and wizards are time-consuming. The problem is that as a consequence, refactoring tools disrupt the programmer's workflow and are perceived to be slower than refactoring by hand. In this paper we present two new user interfaces to Eclipse's existing refactoring engine: marking menus and refactoring cues. Both are designed to increase programming velocity by keeping the tool out of the programmer's way.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2004\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Supporting Java Traits in Eclipse.\n \n\n\n \n Quitslund, P. J.; Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n In Proceedings of the 2004 OOPSLA Workshop on Eclipse Technology eXchange (ETX), of ETX '04, pages 37–41, New York, NY, USA, 2004. ACM\n \n\n\n\n
\n\n\n\n \n \n \"SupportingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Quitslund2004Supporting,\n    abstract = {{Traits are a language technology that complements inheritance as a means for code reuse and class structuring. Traits encapsulate collections of methods so that they can be used and reused anywhere in the inheritance hierarchy. An important property of traits is that classes structured with traits have the same semantics as classes structured without them. With environment support, a programmer can move freely between views of the system with or without its component traits. In this paper we describe an environment for programming with traits for Java implemented in Eclipse.}},\n    address = {New York, NY, USA},\n    author = {Quitslund, Philip J. and Murphy-Hill, Emerson and Black, Andrew P.},\n    booktitle = {Proceedings of the 2004 OOPSLA Workshop on Eclipse Technology eXchange (ETX)},\n    citeulike-article-id = {471630},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/etx04.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1066129.1066137},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1066129.1066137},\n    doi = {10.1145/1066129.1066137},\n    howpublished = {4. Workshop},\n    keywords = {self},\n    location = {Vancouver, British Columbia, Canada},\n    pages = {37--41},\n    posted-at = {2013-10-16 17:37:50},\n    priority = {0},\n    publisher = {ACM},\n    series = {ETX '04},\n    title = {{Supporting Java Traits in Eclipse}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/etx04.pdf},\n    year = {2004}\n}\n\n
\n
\n\n\n
\n Traits are a language technology that complements inheritance as a means for code reuse and class structuring. Traits encapsulate collections of methods so that they can be used and reused anywhere in the inheritance hierarchy. An important property of traits is that classes structured with traits have the same semantics as classes structured without them. With environment support, a programmer can move freely between views of the system with or without its component traits. In this paper we describe an environment for programming with traits for Java implemented in Eclipse.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n\n\n\n
\n
\n\n
\n
\n  \n 5. Demonstration\n \n \n (3)\n \n \n
\n
\n \n \n
\n
\n  \n 2017\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Cheetah: Just-in-Time Taint Analysis for Android Apps.\n \n\n\n \n Do, L. N. Q.; Ali, K.; Livshits, B.; Bodden, E.; Smith, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the International Conference of Software Engineering, 2017. \n \n\n\n\n
\n\n\n\n \n \n \"Cheetah:Paper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{NguyenICSE17demo,\n    author = {Lisa Nguyen Quang Do and Karim Ali and Benjamin Livshits and Eric Bodden and Justin Smith and Emerson Murphy-Hill},\n    booktitle = {Proceedings of the International Conference of Software Engineering},\n    howpublished = {5. Demonstration},\n    keywords = {program\\_analysis},\n    title = {Cheetah: Just-in-Time Taint Analysis for Android Apps},\n    url = {https://people.engr.ncsu.edu/ermurph3/papers/icse17demo.pdf},\n    year = {2017}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2011\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n BeneFactor: a Flexible Refactoring Tool for Eclipse.\n \n\n\n \n Ge, X.; and Murphy-Hill, E.\n\n\n \n\n\n\n In Proceedings of the ACM International Conference on Object Oriented Programming Systems Languages and Applications Companion, of SPLASH '11, pages 19–20, New York, NY, USA, 2011. ACM\n \n\n\n\n
\n\n\n\n \n \n \"BeneFactor:Paper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Ge2011BeneFactor,\n    abstract = {{Although broadly available in major software development environments, refactoring tools are still underused. One of the reasons for this underuse is that existing refactoring tools assume that a developer recognizes that she is going to refactor before she even begins. In this paper, we present a flexible refactoring tool called BeneFactor that can be invoked after refactoring begins to safely complete a refactoring change.}},\n    address = {New York, NY, USA},\n    author = {Ge, Xi and Murphy-Hill, Emerson},\n    booktitle = {Proceedings of the ACM International Conference on Object Oriented Programming Systems Languages and Applications Companion},\n    citeulike-article-id = {11237171},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/SPLASH11Demo.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=2048157},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/2048147.2048157},\n    doi = {10.1145/2048147.2048157},\n    howpublished = {5. Demonstration},\n    isbn = {978-1-4503-0942-4},\n    keywords = {refactoring, self},\n    location = {Portland, Oregon, USA},\n    pages = {19--20},\n    posted-at = {2013-10-16 17:44:11},\n    priority = {2},\n    publisher = {ACM},\n    series = {SPLASH '11},\n    title = {{BeneFactor: a Flexible Refactoring Tool for Eclipse}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/SPLASH11Demo.pdf},\n    year = {2011}\n}\n\n
\n
\n\n\n
\n Although broadly available in major software development environments, refactoring tools are still underused. One of the reasons for this underuse is that existing refactoring tools assume that a developer recognizes that she is going to refactor before she even begins. In this paper, we present a flexible refactoring tool called BeneFactor that can be invoked after refactoring begins to safely complete a refactoring change.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2006\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Tools for a successful refactoring.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n In Companion to the 21st ACM SIGPLAN Conference on Object-Oriented Programming Languages, Systems, and Applications (OOPSLA), pages 694–695, New York, NY, USA, 2006. ACM Press\n \n\n\n\n
\n\n\n\n \n \n \"ToolsPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2006Tools,\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    booktitle = {Companion to the 21st ACM SIGPLAN Conference on Object-Oriented Programming Languages, Systems, and Applications (OOPSLA)},\n    citeulike-article-id = {967620},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/oopsla06demo.pdf},\n    citeulike-linkout-1 = {http://portal.acm.org/citation.cfm?id=1176678},\n    citeulike-linkout-2 = {http://dx.doi.org/10.1145/1176617.1176678},\n    doi = {10.1145/1176617.1176678},\n    howpublished = {5. Demonstration},\n    isbn = {159593491X},\n    keywords = {refactoring, self},\n    pages = {694--695},\n    posted-at = {2013-10-16 17:34:34},\n    priority = {0},\n    publisher = {ACM Press},\n    title = {{Tools for a successful refactoring}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/oopsla06demo.pdf},\n    year = {2006}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n\n\n\n
\n
\n\n
\n
\n  \n 6. Poster\n \n \n (6)\n \n \n
\n
\n \n \n
\n
\n  \n 2014\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n How the Sando search tool recommends queries.\n \n\n\n \n Ge, X.; Shepherd, D.; Damevski, K.; and Murphy-Hill, E.\n\n\n \n\n\n\n In IEEE Conference on Software Maintenance, pages 425–428, February 2014. IEEE\n \n\n\n\n
\n\n\n\n \n \n \"HowPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Ge2014How,\n    author = {Ge, Xi and Shepherd, D. and Damevski, K. and Murphy-Hill, Emerson},\n    booktitle = {IEEE Conference on Software Maintenance},\n    citeulike-article-id = {13119864},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1109/csmr-wcre.2014.6747210},\n    citeulike-linkout-1 = {http://ieeexplore.ieee.org/xpls/abs\\_all.jsp?arnumber=6747210},\n    doi = {10.1109/csmr-wcre.2014.6747210},\n    howpublished = {6. Poster},\n    institution = {NC State Univ., Raleigh, NC, USA},\n    keywords = {self},\n    month = feb,\n    pages = {425--428},\n    posted-at = {2014-03-28 21:00:59},\n    priority = {2},\n    publisher = {IEEE},\n    title = {{How the Sando search tool recommends queries}},\n    url = {http://dx.doi.org/10.1109/csmr-wcre.2014.6747210},\n    year = {2014}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2013\n \n \n (3)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n People-First Tourism: Creating Sustainable and Dignified Livelihoods Through IT-Enabled Entrepreneurship Globally.\n \n\n\n \n LaPan, C.; Peroff, D.; Mao, Y.; Birendra, K. C.; Starr, H.; Morgan, J.; Brown, M.; Hitchins, S.; Morais, D.; Wallace, T.; Brothers, G.; Bass, J.; Baker, T.; and Murphy-Hill, E.\n\n\n \n\n\n\n 6. Poster, April 2013.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{LaPan2013PeopleFirst,\n    author = {LaPan, Chantell and Peroff, Deidre and Mao, Yuchen and Birendra, K. C. and Starr, Holli and Morgan, Jon and Brown, Michael and Hitchins, Spencer and Morais, Duarte and Wallace, Tim and Brothers, Gene and Bass, John and Baker, Ted and Murphy-Hill, Emerson},\n    booktitle = {Global Engagement Expo},\n    citeulike-article-id = {12716961},\n    howpublished = {6. Poster},\n    keywords = {p1t, self},\n    month = apr,\n    posted-at = {2013-10-16 15:46:01},\n    priority = {2},\n    title = {{People-First Tourism: Creating Sustainable and Dignified Livelihoods Through IT-Enabled Entrepreneurship Globally}},\n    year = {2013}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Developing a User Profile to Predict Phishing Susceptibility and Security Technology Acceptance.\n \n\n\n \n Hong, K.; Kelley, C.; Murphy-Hill, E.; and Mayhorn, C.\n\n\n \n\n\n\n 6. Poster, March 2013.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{Hong2013Developing,\n    author = {Hong, KyungWha and Kelley, Chris and Murphy-Hill, Emerson and Mayhorn, Chris},\n    booktitle = {Science of Security Lablet, Industry Day},\n    citeulike-article-id = {12716966},\n    howpublished = {6. Poster},\n    keywords = {nsa, phishing, security, self},\n    month = mar,\n    posted-at = {2013-10-16 15:45:31},\n    priority = {2},\n    title = {{Developing a User Profile to Predict Phishing Susceptibility and Security Technology Acceptance}},\n    year = {2013}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n An Adoption Model of Secure Software Development Tools.\n \n\n\n \n Witschey, J.; and Murphy-Hill, E.\n\n\n \n\n\n\n 6. Poster, March 2013.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{Witschey2013Adoption,\n    author = {Witschey, Jim and Murphy-Hill, Emerson},\n    booktitle = {Science of Security Lablet, Industry Day},\n    citeulike-article-id = {12716974},\n    howpublished = {6. Poster},\n    keywords = {adoption, nsa, security, self},\n    month = mar,\n    posted-at = {2013-10-16 15:43:33},\n    priority = {2},\n    title = {{An Adoption Model of Secure Software Development Tools}},\n    year = {2013}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2012\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n An Adoption Model of Secure Software Development Tools.\n \n\n\n \n Murphy-Hill, E.; Xiao, S.; and Witschey, J.\n\n\n \n\n\n\n 6. Poster, 2012.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2012Adoption,\n    author = {Murphy-Hill, Emerson and Xiao, Shundan and Witschey, Jim},\n    booktitle = {Science of Security Lablet, Community Meeting},\n    citeulike-article-id = {12717000},\n    howpublished = {6. Poster},\n    keywords = {adoption, self},\n    pages = {February},\n    posted-at = {2013-10-16 17:50:16},\n    priority = {2},\n    title = {{An Adoption Model of Secure Software Development Tools}},\n    year = {2012}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Developing a User Profile to Predict Phishing Susceptibility and Security Technology Acceptance.\n \n\n\n \n Mayhorn, C.; Hong, K. W.; Kelley, C.; and Murphy-Hill, E.\n\n\n \n\n\n\n 6. Poster, November 2012.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{Mayhorn2012Developing,\n    author = {Mayhorn, Chris and Hong, Kyung W. and Kelley, Chris and Murphy-Hill, Emerson},\n    booktitle = {Science of Security Lablet, Quarterly Meeting},\n    citeulike-article-id = {12716995},\n    howpublished = {6. Poster},\n    keywords = {nsa, phishing, security, self},\n    month = nov,\n    posted-at = {2013-10-16 15:42:33},\n    priority = {2},\n    title = {{Developing a User Profile to Predict Phishing Susceptibility and Security Technology Acceptance}},\n    year = {2012}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2008\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Scalable, Expressive, and Context-Sensitive Code Smell Display.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n In Companion to the 23rd ACM SIGPLAN Conference on Object-Oriented Programming Systems Languages and Applications, of OOPSLA Companion '08, pages 771–772, New York, NY, USA, 2008. ACM\n \n\n\n\n
\n\n\n\n \n \n \"Scalable,Paper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2008Scalable,\n    abstract = {{Code smell detectors can potentially help programmers identify opportunities to improve the design of software through refactoring. Unfortunately, the user interfaces to existing detectors often do not align with how programmers typically refactor. I argue the importance of scalability, expressivity, and context-sensitivity when displaying smells, and present a prototype tool that embodies these properties.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Companion to the 23rd ACM SIGPLAN Conference on Object-Oriented Programming Systems Languages and Applications},\n    citeulike-article-id = {8345110},\n    citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=1449854},\n    citeulike-linkout-1 = {http://dx.doi.org/10.1145/1449814.1449854},\n    doi = {10.1145/1449814.1449854},\n    howpublished = {6. Poster},\n    isbn = {978-1-60558-220-7},\n    keywords = {refactoring, self},\n    location = {Nashville, TN, USA},\n    pages = {771--772},\n    posted-at = {2013-10-16 17:02:30},\n    priority = {2},\n    publisher = {ACM},\n    series = {OOPSLA Companion '08},\n    title = {{Scalable, Expressive, and Context-Sensitive Code Smell Display}},\n    url = {http://dx.doi.org/10.1145/1449814.1449854},\n    year = {2008}\n}\n\n
\n
\n\n\n
\n Code smell detectors can potentially help programmers identify opportunities to improve the design of software through refactoring. Unfortunately, the user interfaces to existing detectors often do not align with how programmers typically refactor. I argue the importance of scalability, expressivity, and context-sensitivity when displaying smells, and present a prototype tool that embodies these properties.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2007\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Flossing Regularly — The Key to Healthy Software.\n \n\n\n \n Murphy-Hill, E.; and Black, A. P.\n\n\n \n\n\n\n In European Conference on Object-Oriented Programming (ECOOP), 2007. \n \n\n\n\n
\n\n\n\n \n \n \"FlossingPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2007Flossing,\n    author = {Murphy-Hill, Emerson and Black, Andrew P.},\n    booktitle = {European Conference on Object-Oriented Programming (ECOOP)},\n    citeulike-article-id = {12716768},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/posters/ecoop07poster.pdf},\n    howpublished = {6. Poster},\n    keywords = {refactoring, self},\n    posted-at = {2013-10-16 17:02:47},\n    priority = {2},\n    title = {{Flossing Regularly — The Key to Healthy Software}},\n    url = {http://people.engr.ncsu.edu/ermurph3/posters/ecoop07poster.pdf},\n    year = {2007}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Activating Refactorings Faster.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n In Companion to the 22nd ACM SIGPLAN Conference on Object-Oriented Programming Systems and Applications Companion (OOPSLA), Student Research Competition (3rd Place), of OOPSLA '07, pages 925–926, New York, NY, USA, 2007. ACM\n \n\n\n\n
\n\n\n\n \n \n \"ActivatingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n  \n \n abstract \n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2007Activating,\n    abstract = {{Refactoring tools promise to increase the speed at which programmers write code, but programmers report that contemporary tools sometimes slow them down. Some of that slowdown can be attributed to the time it takes to activate refactoring tools, typically with a combination of code selection, hotkeys, linear menus, and wizard interfaces. In this paper, I present pie menus and refactoring cues, two new mechanisms for activating refactoring tools. These mechanisms were designed to accommodate how program-mers want to refactor and to make good on the promise of refactoring tools to help programmers write code faster.}},\n    address = {New York, NY, USA},\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Companion to the 22nd ACM SIGPLAN Conference on Object-Oriented Programming Systems and Applications Companion (OOPSLA), Student Research Competition (3rd Place)},\n    citeulike-article-id = {12716782},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/src07.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/posters/src07poster.pdf},\n    citeulike-linkout-2 = {http://portal.acm.org/citation.cfm?id=1297846.1297948},\n    citeulike-linkout-3 = {http://dx.doi.org/10.1145/1297846.1297948},\n    doi = {10.1145/1297846.1297948},\n    howpublished = {6. Poster},\n    isbn = {978-1-59593-865-7},\n    keywords = {refactoring, self},\n    location = {Montreal, Quebec, Canada},\n    pages = {925--926},\n    posted-at = {2013-10-16 17:02:38},\n    priority = {2},\n    publisher = {ACM},\n    series = {OOPSLA '07},\n    title = {{Activating Refactorings Faster}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/src07.pdf},\n    year = {2007}\n}\n\n
\n
\n\n\n
\n Refactoring tools promise to increase the speed at which programmers write code, but programmers report that contemporary tools sometimes slow them down. Some of that slowdown can be attributed to the time it takes to activate refactoring tools, typically with a combination of code selection, hotkeys, linear menus, and wizard interfaces. In this paper, I present pie menus and refactoring cues, two new mechanisms for activating refactoring tools. These mechanisms were designed to accommodate how program-mers want to refactor and to make good on the promise of refactoring tools to help programmers write code faster.\n
\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2003\n \n \n (3)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n The Canopy Database Project: Component-Driven Database Design & Visualization.\n \n\n\n \n Cushing, J. B.; Nadkarni, N.; Finch, M.; Kim, Y.; and Murphy-Hill, E.\n\n\n \n\n\n\n 6. Poster, 2003.\n \n\n\n\n
\n\n\n\n \n \n \"ThePaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{Cushing2003Canopy,\n    author = {Cushing, Judith B. and Nadkarni, Nalini and Finch, Michael and Kim, Youngmi and Murphy-Hill, Emerson},\n    booktitle = {IEEE Visualization Conference},\n    citeulike-article-id = {471637},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/posters/vis03poster.pdf},\n    howpublished = {6. Poster},\n    keywords = {self},\n    posted-at = {2013-10-16 17:35:01},\n    priority = {0},\n    title = {{The Canopy Database Project: Component-Driven Database Design \\& Visualization}},\n    url = {http://people.engr.ncsu.edu/ermurph3/posters/vis03poster.pdf},\n    year = {2003}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n The Trait Extractor: A Tool for Generating Traits in Java.\n \n\n\n \n Murphy-Hill, E.; and Black, A.\n\n\n \n\n\n\n In Consortium for Computing in Colleges, 2003. \n \n\n\n\n
\n\n\n\n \n \n \"ThePaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2003Trait,\n    author = {Murphy-Hill, Emerson and Black, Andrew},\n    booktitle = {Consortium for Computing in Colleges},\n    citeulike-article-id = {471639},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/posters/ccsc04.vsd},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/posters/ccsc04.pdf},\n    howpublished = {6. Poster},\n    keywords = {self},\n    posted-at = {2013-10-16 17:34:55},\n    priority = {0},\n    title = {{The Trait Extractor: A Tool for Generating Traits in Java}},\n    url = {http://people.engr.ncsu.edu/ermurph3/posters/ccsc04.vsd},\n    year = {2003}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Traits: Evaluating a Language Feature | Object-Oriented Candyland or Inheritance Quagmire?.\n \n\n\n \n Murphy-Hill, E.; Black, A. P.; and Cushing, J.\n\n\n \n\n\n\n In Consortium for Computing Sciences in Colleges, 2003. \n \n\n\n\n
\n\n\n\n \n \n \"Traits:Paper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{MurphyHill2003Traits,\n    author = {Murphy-Hill, Emerson and Black, Andrew P. and Cushing, Judy},\n    booktitle = {Consortium for Computing Sciences in Colleges},\n    citeulike-article-id = {12716747},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/posters/ccsc03.pdf},\n    howpublished = {6. Poster},\n    keywords = {self},\n    posted-at = {2013-10-16 17:02:59},\n    priority = {2},\n    title = {{Traits: Evaluating a Language Feature | Object-Oriented Candyland or Inheritance Quagmire?}},\n    url = {http://people.engr.ncsu.edu/ermurph3/posters/ccsc03.pdf},\n    year = {2003}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n\n\n\n
\n
\n\n
\n
\n  \n 7. Presentation\n \n \n (9)\n \n \n
\n
\n \n \n
\n
\n  \n 2013\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n An Adoption Theory of Secure Development Tools.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, 2013.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2013Adoption,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {University of California, Irvine},\n    citeulike-article-id = {12717109},\n    howpublished = {7. Presentation},\n    keywords = {adoption, nsa, security, self},\n    posted-at = {2013-10-16 15:19:37},\n    priority = {2},\n    title = {{An Adoption Theory of Secure Development Tools}},\n    year = {2013}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Helping Developers Find Useful Tools.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, 2013.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2013Helping,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {University of North Carolina, Greenville},\n    citeulike-article-id = {12717117},\n    howpublished = {7. Presentation},\n    keywords = {adoption, discovery, self},\n    posted-at = {2013-10-16 15:15:39},\n    priority = {2},\n    title = {{Helping Developers Find Useful Tools}},\n    year = {2013}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2012\n \n \n (4)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n The App Explosion and What It Means to All of Us.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, September 2012.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2012App,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Triangle Black Data Processing Association Meeting, RTP, North Carolina},\n    citeulike-article-id = {12717008},\n    howpublished = {7. Presentation},\n    keywords = {adoption, self},\n    month = sep,\n    posted-at = {2013-10-16 15:37:24},\n    priority = {2},\n    title = {{The App Explosion and What It Means to All of Us}},\n    year = {2012}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n The Design of Bug Fixes.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, August 2012.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2012Design,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Microsoft Research, Redmond, Washington},\n    citeulike-article-id = {12717012},\n    howpublished = {7. Presentation},\n    keywords = {self},\n    month = aug,\n    posted-at = {2013-10-16 15:37:11},\n    priority = {2},\n    title = {{The Design of Bug Fixes}},\n    year = {2012}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Why Don't Software Developers Use Their Tools?.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, March 2012.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2012Why,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Google, Atlanta, Georgia},\n    citeulike-article-id = {12717017},\n    howpublished = {7. Presentation},\n    keywords = {adoption, self},\n    month = mar,\n    posted-at = {2013-10-16 15:35:55},\n    priority = {2},\n    title = {{Why Don't Software Developers Use Their Tools?}},\n    year = {2012}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Helping Developers Find Useful Tools.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, March 2012.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2012Helping,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Keynote at the Symposium on Augmenting Software Developer Support to Improve Productivity},\n    citeulike-article-id = {12717021},\n    howpublished = {7. Presentation},\n    keywords = {adoption, self},\n    month = mar,\n    posted-at = {2013-10-16 15:35:16},\n    priority = {2},\n    title = {{Helping Developers Find Useful Tools}},\n    year = {2012}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2011\n \n \n (3)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Going green with refactoring: sustaining the \"worldwide virtual machine\".\n \n\n\n \n Fraser, S.; Murphy-Hill, E.; Wild, W.; Yoder, J.; and Zhu, B. Q.\n\n\n \n\n\n\n In Panel at SPLASH, pages 171+, New York, New York, USA, 2011. ACM Press\n \n\n\n\n
\n\n\n\n \n \n \"GoingPaper\n  \n \n\n \n \n doi\n  \n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@inproceedings{Fraser2011Going,\n    address = {New York, New York, USA},\n    author = {Fraser, Steven and Murphy-Hill, Emerson and Wild, Werner and Yoder, Joseph and Zhu, Bo Q.},\n    booktitle = {Panel at SPLASH},\n    citeulike-article-id = {12717025},\n    citeulike-linkout-0 = {http://dx.doi.org/10.1145/2048147.2048193},\n    doi = {10.1145/2048147.2048193},\n    howpublished = {7. Presentation},\n    isbn = {9781450309424},\n    keywords = {refactoring, self},\n    location = {Portland, Oregon, USA},\n    pages = {171+},\n    posted-at = {2013-10-16 15:32:08},\n    priority = {2},\n    publisher = {ACM Press},\n    title = {{Going green with refactoring: sustaining the "worldwide virtual machine"}},\n    url = {http://dx.doi.org/10.1145/2048147.2048193},\n    year = {2011}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n How are Developers Using Refactoring Tools?.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, July 2011.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2011How,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Microsoft Faculty Summit, Redmond, WA},\n    citeulike-article-id = {12717030},\n    howpublished = {7. Presentation},\n    keywords = {adoption, refactoring, self},\n    month = jul,\n    posted-at = {2013-10-16 15:27:13},\n    priority = {2},\n    title = {{How are Developers Using Refactoring Tools?}},\n    year = {2011}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n Why Don't Software Developers Use Their Tools?.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, February 2011.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2011Why,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Microsoft Research, Redmond, Washington},\n    citeulike-article-id = {12717032},\n    howpublished = {7. Presentation},\n    keywords = {adoption, self},\n    month = feb,\n    posted-at = {2013-10-16 15:26:52},\n    priority = {2},\n    title = {{Why Don't Software Developers Use Their Tools?}},\n    year = {2011}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2010\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Why Don't Software Developers Use Their Tools?.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, September 2010.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2010Why,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {ABB Research, Raleigh, NC},\n    citeulike-article-id = {12717037},\n    howpublished = {7. Presentation},\n    keywords = {adoption, self},\n    month = sep,\n    posted-at = {2013-10-16 15:21:55},\n    priority = {2},\n    title = {{Why Don't Software Developers Use Their Tools?}},\n    year = {2010}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n How Are People Using Eclipse?.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, 2010.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2010How,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Eclipse Demo Camp, Vancouver, British Columbia},\n    citeulike-article-id = {12717040},\n    howpublished = {7. Presentation},\n    keywords = {adoption, self},\n    posted-at = {2013-10-16 15:21:42},\n    priority = {2},\n    title = {{How Are People Using Eclipse?}},\n    year = {2010}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2009\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Finding Code Smells in Eclipse.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, June 2009.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2009Finding,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Eclipse Demo Camp, Portland, Oregon},\n    citeulike-article-id = {12717045},\n    howpublished = {7. Presentation},\n    keywords = {refactoring, self},\n    month = jun,\n    posted-at = {2013-10-16 15:21:32},\n    priority = {2},\n    title = {{Finding Code Smells in Eclipse}},\n    year = {2009}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2007\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Refactoring Tools that People Actually Use.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, September 2007.\n \n\n\n\n
\n\n\n\n \n \n \"RefactoringPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2007Refactoring,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Presentation to the Portland Java Users' Group},\n    citeulike-article-id = {12716737},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/presentations/pjug.pdf},\n    day = {18},\n    howpublished = {7. Presentation},\n    keywords = {refactoring, self},\n    month = sep,\n    posted-at = {2013-10-16 17:03:20},\n    priority = {2},\n    title = {{Refactoring Tools that People Actually Use}},\n    url = {http://people.engr.ncsu.edu/ermurph3/presentations/pjug.pdf},\n    year = {2007}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2006\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Alternative Interfaces to Eclipse Refactoring Tools.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, 2006.\n \n\n\n\n
\n\n\n\n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2006Alternative,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Eclipse Demo Camp, Portland, Oregon},\n    citeulike-article-id = {12717048},\n    howpublished = {7. Presentation},\n    keywords = {self},\n    posted-at = {2013-10-16 15:21:22},\n    priority = {2},\n    title = {{Alternative Interfaces to Eclipse Refactoring Tools}},\n    year = {2006}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2005\n \n \n (2)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n What a Guy Who's Still In School Thinks.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, September 2005.\n \n\n\n\n
\n\n\n\n \n \n \"WhatPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2005What,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Panel: Life After Evergreen},\n    citeulike-article-id = {12716703},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/presentations/evergreen05.pdf},\n    day = {22},\n    howpublished = {7. Presentation},\n    keywords = {self},\n    month = sep,\n    posted-at = {2013-10-16 17:44:52},\n    priority = {2},\n    title = {{What a Guy Who's Still In School Thinks}},\n    url = {http://people.engr.ncsu.edu/ermurph3/presentations/evergreen05.pdf},\n    year = {2005}\n}\n\n
\n
\n\n\n\n
\n\n\n
\n \n\n \n \n \n\n A Vehicle Traffic Analysis Tool.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, 2005.\n \n\n\n\n
\n\n\n\n \n \n \"APaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2005Vehicle,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {European Smalltalk Users Group},\n    citeulike-article-id = {471634},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/presentations/esug05.ppt},\n    howpublished = {7. Presentation},\n    keywords = {self},\n    posted-at = {2013-10-16 17:36:50},\n    priority = {0},\n    title = {{A Vehicle Traffic Analysis Tool}},\n    url = {http://people.engr.ncsu.edu/ermurph3/presentations/esug05.ppt},\n    year = {2005}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2004\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n LegalTransform: a Framework for Making Legal Documents Accessible to Humans.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 7. Presentation, 2004.\n \n\n\n\n
\n\n\n\n \n \n \"LegalTransform:Paper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2004LegalTransform,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Olympia Microcomputer Users Group},\n    citeulike-article-id = {471636},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/presentations/omug.pdf},\n    howpublished = {7. Presentation},\n    keywords = {self},\n    posted-at = {2013-10-16 17:42:57},\n    priority = {0},\n    title = {{LegalTransform: a Framework for Making Legal Documents Accessible to Humans}},\n    url = {http://people.engr.ncsu.edu/ermurph3/presentations/omug.pdf},\n    year = {2004}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n\n\n\n
\n
\n\n
\n
\n  \n 8. Other\n \n \n (3)\n \n \n
\n
\n \n \n
\n
\n  \n 2009\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Programmer-Friendly Refactoring Tools.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n Ph.D. Thesis, February 2009.\n \n\n\n\n
\n\n\n\n \n \n \"Programmer-FriendlyPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n  \n \n 3 downloads\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@phdthesis{MurphyHill2009ProgrammerFriendly,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Dissertation},\n    citeulike-article-id = {12716742},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/dissertation.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/presentations/dissertationPresentation.pptx},\n    day = {28},\n    howpublished = {8. Other},\n    institution = {Portland State University},\n    keywords = {refactoring, self},\n    month = feb,\n    posted-at = {2013-10-16 17:03:10},\n    priority = {2},\n    title = {{Programmer-Friendly Refactoring Tools}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/dissertation.pdf},\n    year = {2009}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2007\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Programmer-Friendly Refactoring Tools.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 8. Other, May 2007.\n \n\n\n\n
\n\n\n\n \n \n \"Programmer-FriendlyPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2007ProgrammerFriendly,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Thesis Proposal},\n    citeulike-article-id = {12716729},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/ThesisProposal.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/presentations/ThesisProposalPresentation.pdf},\n    day = {27},\n    howpublished = {8. Other},\n    institution = {Portland State University},\n    keywords = {refactoring, self},\n    month = may,\n    posted-at = {2013-10-16 17:03:32},\n    priority = {2},\n    title = {{Programmer-Friendly Refactoring Tools}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/ThesisProposal.pdf},\n    year = {2007}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n
\n
\n  \n 2006\n \n \n (1)\n \n \n
\n
\n \n \n
\n \n\n \n \n \n\n Improving Refactoring with Alternate Program Views.\n \n\n\n \n Murphy-Hill, E.\n\n\n \n\n\n\n 8. Other, May 2006.\n \n\n\n\n
\n\n\n\n \n \n \"ImprovingPaper\n  \n \n\n \n\n bibtex\n \n\n \n\n \n  \n \n 1 download\n \n \n\n \n \n \n \n \n \n \n\n\n\n
\n
@misc{MurphyHill2006Improving,\n    author = {Murphy-Hill, Emerson},\n    booktitle = {Research Proficiency Exam},\n    citeulike-article-id = {12716723},\n    citeulike-linkout-0 = {http://people.engr.ncsu.edu/ermurph3/papers/rpe.pdf},\n    citeulike-linkout-1 = {http://people.engr.ncsu.edu/ermurph3/presentations/rpePresentation.ppt},\n    day = {19},\n    howpublished = {8. Other},\n    keywords = {refactoring, self},\n    month = may,\n    posted-at = {2013-10-16 17:28:42},\n    priority = {2},\n    title = {{Improving Refactoring with Alternate Program Views}},\n    url = {http://people.engr.ncsu.edu/ermurph3/papers/rpe.pdf},\n    year = {2006}\n}\n\n
\n
\n\n\n\n
\n\n\n\n\n\n
\n
\n\n\n\n\n
\n
\n\n\n\n\n
\n\n\n \n
\n
\n \n

Embedding in another Page

\n
\n
\n\n

\n Copy & paste any of the following snippets into an existing\n page to embed this page. For more details see the\n documention.\n

\n\n JavaScript\n (easiest)\n
\n \n <script src=\"https://bibbase.org/show?bib=https://raw.githubusercontent.com/DeveloperLiberationFront/bibtex-library/master/our-papers.bib&css=rawgit.com/DeveloperLiberationFront/bibtex-library/master/bibstyle.css&jsonp=1&group0=howpublished&group1=year&theme=simple&filter=author_short:Murphy-Hill&jsonp=1\"></script>\n \n
\n\n PHP\n
\n \n <?php\n $contents = file_get_contents(\"https://bibbase.org/show?bib=https://raw.githubusercontent.com/DeveloperLiberationFront/bibtex-library/master/our-papers.bib&css=rawgit.com/DeveloperLiberationFront/bibtex-library/master/bibstyle.css&jsonp=1&group0=howpublished&group1=year&theme=simple&filter=author_short:Murphy-Hill\");\n print_r($contents);\n ?>\n \n
\n\n iFrame\n (not recommended)\n
\n \n <iframe src=\"https://bibbase.org/show?bib=https://raw.githubusercontent.com/DeveloperLiberationFront/bibtex-library/master/our-papers.bib&css=rawgit.com/DeveloperLiberationFront/bibtex-library/master/bibstyle.css&jsonp=1&group0=howpublished&group1=year&theme=simple&filter=author_short:Murphy-Hill\"></iframe>\n \n
\n\n\n
\n
\n \n
\n
\n\n \n \n \n \n\n
\n"}; document.write(bibbase_data.data);