Continuity gap between video demo and source code

[stevepiercy]

This time I paid extremely careful attention to the content of the videos while following along.

In this video:
https://training.talkpython.fm/player/course/python-for-entrepreneurs-build-and-launch-your-online-business/lecture/51012

I was able to follow along and run the app, and watch the logging from sqlalchemy.

But in the next video, there is a huge leap and gap in continuity.
https://training.talkpython.fm/player/course/python-for-entrepreneurs-build-and-launch-your-online-business/lecture/51012

It was impossible to get the app to run if you followed the videos exactly in sequence. There are a bunch of missing files and code that are not mentioned up to this point.

Sure, I could jump ahead to the end and just run the code from the repo for the chapter, but that omits steps that are necessary to reach the destination.

[knutfh]

I find similar discrepancies too. Was forced to take a break from the course, and when I'm resuming with chapter 4 now, I find it difficult to follow this lecture "Remember the site we built? It's back!": https://training.talkpython.fm/player/course/python-for-entrepreneurs-build-and-launch-your-online-business/lecture/50802

The reorganization that happens at 01:40 makes changes to some files, including mytemplate.pt, where we suddenly have a reference to build_cache_id(). There is also a new site.css file that is not in the start_4_blue_yellow_app directory on Github.

I wish that checking out a folder from the Github repo would leave us with a state that can be used when starting a new chapter.

@mikeckennedy Do you have any comments on this? I really want to get going again.

[datatalking]

@knutfh @stevepiercy I'm right there with you two.

What I would suggest is that this is a strong correlation between how the real world of software works with back and forth vs a tutorial... which I will agree has a few flashbacks and flashforwards in the script but overall its one of the best out there.

Perhaps we could work together to crowdsource the solution and bring that to Michael?

Maybe we three could fix the code, create a repo and share it?

[stevepiercy]

It would be wise to get consensus with @mikeckennedy before doing any work.

As an example proposal, in Pyramid docs, we handle steps in our tutorials by providing the source files at the end of each step:

https://docs.pylonsproject.org/projects/pyramid/en/1.9-branch/tutorials/wiki2/

Correlates to:

https://github.com/Pylons/pyramid/tree/1.9-branch/docs/tutorials/wiki2/src