Bug writeups
Jun. 30th, 2010 07:38 am![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
deniseSince ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
ninetydegrees posted recently about dev journals, and since I'd like to see ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_dev_training used as a repository of tutorials and coaching as well as a place for people to ask questions, I thought about the bug walkthroughs a few of us were doing last year and wanted to know if people would be interested in bringing them back.
I'm envisioning posts here indw_dev_training with anything from things you learned while working on the bug, the steps you took to figure out how to approach the bug, the wrong turns you took while working on the bug, things you tried that you thought should work but didn't and how you figured out what was going wrong, etc, etc. It could be anything from the immensely involved to a few quick bullet points explaining the process you took through the bug.
It wouldn't be anything that anybody would be required to do, but I know that if others were doing this too, it would inspire me to keep better notes about my dev work and my bug-solving process, and to write them up for others to learn from. I really appreciate seeing others' dev notes, because a) it reminds me that I'm not alone in making little errors like forgetting braces or semicolons; b) it gives me insight about how people approach problems, which I can take back to apply to my work; c) it reminds me to work on more bugs!
So, a poll:
ninetydegrees posted recently about dev journals, and since I'd like to see dw_dev_training used as a repository of tutorials and coaching as well as a place for people to ask questions, I thought about the bug walkthroughs a few of us were doing last year and wanted to know if people would be interested in bringing them back.I'm envisioning posts here in
dw_dev_training with anything from things you learned while working on the bug, the steps you took to figure out how to approach the bug, the wrong turns you took while working on the bug, things you tried that you thought should work but didn't and how you figured out what was going wrong, etc, etc. It could be anything from the immensely involved to a few quick bullet points explaining the process you took through the bug.It wouldn't be anything that anybody would be required to do, but I know that if others were doing this too, it would inspire me to keep better notes about my dev work and my bug-solving process, and to write them up for others to learn from. I really appreciate seeing others' dev notes, because a) it reminds me that I'm not alone in making little errors like forgetting braces or semicolons; b) it gives me insight about how people approach problems, which I can take back to apply to my work; c) it reminds me to work on more bugs!
So, a poll:
Open to: Registered Users, detailed results viewable to: All, participants: 26
I find writeups of other people's bug solving process:
View Answers
Helpful
23 (88.5%)
Inspiring
17 (65.4%)
Annoying
1 (3.8%)
Intimidating
3 (11.5%)
Boring
0 (0.0%)
Something else, which I will explain in comments
2 (7.7%)
Assuming we did this regularly, I would write up my bug solving process:
View Answers
Often, whenever I had time/energy
4 (19.0%)
Semi-regularly, if the bug wasn't incredibly basic/boring
9 (42.9%)
Semi-regularly, if the bug was quick
6 (28.6%)
Sometimes, if the bug was really out of the ordinary and I thought someone could learn
11 (52.4%)
Almost never or never (I'd rather code instead!)
2 (9.5%)
Ticky:
