The questions below has been organized under 7 headings and the frequency and importance of the questions can be viewed in the figures below.
- Writing Code c1) What data structures or functions can be use to implement this behaviour?
- Submitting a change s1) Did I make any mistakes in my new code?
- Triaging bugs b1) Is this a legitimate problem?
- Reproducing the Failure r1) What does the failure look like?
- Understanding behavior u1) What code could have caused this behaviour?
- Reasoning about design d1) What is the purpose of this code?
- Maintaining awareness a1) How have resources I depend on changed?
c2) How do I use this data structure of function?
c3) How can I coordinate this with this other data structure or function?
s2) Did I follow my team's conventions?
s3) Which changes are part of this submission?
b2) How difficult will this problem be to fix?
b3) Is it worth fixing?
r2) In what situations does this failure occur?
u2) What's statistically related to this code?
u3) What code caused this program state?
d2) What is the program supposed to do?
d3) Why was this code implemented this way?
d4) What are the implications of this change?
a2) What have my coworkers been doing?
a3) What information was relevant to my task?
Figure 1: Types of information developers sought with search times, percepted importance, availability and accuracy.
Figure 2: Type of information developers sought and the frequency and outcomes of searches, and sources. Common sources are in bold.
No comments:
Post a Comment