Alright, I understand your point and I totally agree. I think the proposal of Alex can be good but well, I guess this is another debate.
Best, Michael Le mardi 27 mars 2012 01:28:59 UTC+2, Russell Keith-Magee a écrit : > > > On 27/03/2012, at 4:59 AM, Michael wrote: > > > Hi, > > > > I do not know if this is the right place so sorry if not. > > I am new to Django for a few months. I love the official django tutorial > and I went through it. > > However, I actually never kept the whole tutorial source code on my PC > so after a while, when I wanted to look at a specific thing I saw in the > tutorial, I just felt bad that I had to do the whole tutorial again to get > the whole project working. > > So I created a public repository on github ( > https://github.com/mike87/django-tuto) with the source code of the django > tutorial and I have thought that it might help people like me, being > between beginner and intermediate that just wanna go through the tutorial > sometimes. > > > > What do you think ? Would it be nice to mention the link at the end of > the tutorial on the documentation ? > > Could it help beginners ? > > Hi Michael, > > Thanks for the suggestion, but we've been down this path before and > abandoned it. > > Once upon a time -- way back in Django's past -- we actually did have the > tutorial code available as part of the Django repository. The problem was > keeping the tutorial code and the tutorial itself in sync. If the two ever > diverged (because someone made a change and forgot to update the code) or > if there was ever an error in the code, then anyone doing the tutorial > would get confused -- and that's the worst possible time to get confused, > since it's our opportunity to convince someone how good Django is. > > There's also the problem that the tutorial goes through 4 steps, and it > would be useful to have the code at the end of each step of the tutorial. > Maintaining 4 tutorial codebases is also a time consuming process. > > Ultimately, the decision was made that there isn't *that* much code in the > tutorial, so it was better to just have the text explanation, and get > people to type the code. There's also a certain amount of evidence from > education circles that this is a good idea anyway -- forcing someone to > actually type the code (and therefore engage with the learning process) has > benefits over just cutting and pasting some pre-prepared code. > > Yours, > Russ Magee %-) > > Le mardi 27 mars 2012 01:28:59 UTC+2, Russell Keith-Magee a écrit : > > > On 27/03/2012, at 4:59 AM, Michael wrote: > > > Hi, > > > > I do not know if this is the right place so sorry if not. > > I am new to Django for a few months. I love the official django tutorial > and I went through it. > > However, I actually never kept the whole tutorial source code on my PC > so after a while, when I wanted to look at a specific thing I saw in the > tutorial, I just felt bad that I had to do the whole tutorial again to get > the whole project working. > > So I created a public repository on github ( > https://github.com/mike87/django-tuto) with the source code of the django > tutorial and I have thought that it might help people like me, being > between beginner and intermediate that just wanna go through the tutorial > sometimes. > > > > What do you think ? Would it be nice to mention the link at the end of > the tutorial on the documentation ? > > Could it help beginners ? > > Hi Michael, > > Thanks for the suggestion, but we've been down this path before and > abandoned it. > > Once upon a time -- way back in Django's past -- we actually did have the > tutorial code available as part of the Django repository. The problem was > keeping the tutorial code and the tutorial itself in sync. If the two ever > diverged (because someone made a change and forgot to update the code) or > if there was ever an error in the code, then anyone doing the tutorial > would get confused -- and that's the worst possible time to get confused, > since it's our opportunity to convince someone how good Django is. > > There's also the problem that the tutorial goes through 4 steps, and it > would be useful to have the code at the end of each step of the tutorial. > Maintaining 4 tutorial codebases is also a time consuming process. > > Ultimately, the decision was made that there isn't *that* much code in the > tutorial, so it was better to just have the text explanation, and get > people to type the code. There's also a certain amount of evidence from > education circles that this is a good idea anyway -- forcing someone to > actually type the code (and therefore engage with the learning process) has > benefits over just cutting and pasting some pre-prepared code. > > Yours, > Russ Magee %-) > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/4kDEEGYsTGAJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
