Skip to content
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

Add file to note workshop response (to learn from) #50

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,12 @@ but rather intended to provide additional insight and knowledge.
It is best if users go through the tutorials and understand the absolute basics
of Django before the workshop.

We have included some `experiences`_ of past workshops using these materials.

.. _Django: https://djangoproject.com
.. _San Diego Python: http://pythonsd.org
.. _Django tutorials: https://docs.djangoproject.com/en/1.5/intro/tutorial01/
.. _experiences: experiences.rst


Tutorials
Expand Down
37 changes: 37 additions & 0 deletions experiences.rst
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 0.0.1`_)

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.

Participant 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 0.0.1: https://github.com/pythonsd/test-driven-django-development/releases/tag/v0.0.1