Towards a Programmer's Apprentice (Again)
Abstract
Programmers are loathe to interrupt their workflow to document their design rationale, leading to frequent errors when software is modified — often much later and by different programmers. A Programmer’s Assistant could interact with the programmer to capture and preserve design rationale, in a natural way that would make rationale capture "cost less than it's worth", and could also detect common flaws in program design. Such a programmer’s assistant was not practical when it was first proposed decades ago, but advances over the years make now the time to revisit the concept, as our prototype shows.
Cite
Text
Shrobe et al. "Towards a Programmer's Apprentice (Again)." AAAI Conference on Artificial Intelligence, 2015. doi:10.1609/AAAI.V29I1.9765Markdown
[Shrobe et al. "Towards a Programmer's Apprentice (Again)." AAAI Conference on Artificial Intelligence, 2015.](https://mlanthology.org/aaai/2015/shrobe2015aaai-programmer/) doi:10.1609/AAAI.V29I1.9765BibTeX
@inproceedings{shrobe2015aaai-programmer,
title = {{Towards a Programmer's Apprentice (Again)}},
author = {Shrobe, Howard Elliot and Katz, Boris and Davis, Randall},
booktitle = {AAAI Conference on Artificial Intelligence},
year = {2015},
pages = {4062-4066},
doi = {10.1609/AAAI.V29I1.9765},
url = {https://mlanthology.org/aaai/2015/shrobe2015aaai-programmer/}
}