-
Notifications
You must be signed in to change notification settings - Fork 36
Add file to note workshop response (to learn from) #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
Experiences with the tutorials | ||
============================== | ||
|
||
November 2, 2013 San Diego Workshop | ||
----------------------------------- | ||
|
||
We did a Django TDD workshop on November 2, 2013 in San Diego based on these | ||
tutorials (`version 1.0`_) | ||
|
||
Teaching Method | ||
~~~~~~~~~~~~~~~ | ||
|
||
We split into 5 groups at large tables, ensuring a reasonable mix of users | ||
that were new and experienced at programming/webdev/Django/TDD. Each user | ||
walked through the tutorials at their own pace. Four of us floated around | ||
the room answering questions and noting everyone's place in the tutorials. | ||
|
||
Most hang-ups were experienced by multiple tables independently. When an issue | ||
was found with the tutorials, one of us would start drafting a pull request | ||
(to improve clarity or fix a bug). We usually merged the pull requests after | ||
at least one other volunteer reviewed it We asked anyone else who had the | ||
issue to refresh the page and see whether the new copy clarified their issue. | ||
|
||
Everyone finished the tutorials in about 5 hours. | ||
|
||
Feedback | ||
~~~~~~~~ | ||
|
||
The feedback was very positive. The primary negative feedback I remember was | ||
that some occasionally felt like they were just copy-pasting. I think this | ||
could be resolved by adding some more explanation for some sections and | ||
encouraging users not to copy-paste (as suggested by Learn Python the Hard | ||
Way). One user also noted that he often forgot to go look at the site after | ||
adding a feature. We should probably ask users to go inspect the relevant | ||
part of the site whenever their tests pass. | ||
|
||
.. _version 1.0: https://github.com/pythonsd/test-driven-django-development/releases/tag/v1.0 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's where that tag came from! I say we reference it as v0.0.1 since that's how rtfd will do it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @davidfischer agreed let's rename it to reference the v0.0.1 tag. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested title: Participant Feedback
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like that title. I also think the file should be renamed to feedback.rst.