#100DaysOfWeb in Python Transcripts
Chapter: Welcome to the course
Lecture: Course flow
0:00 Let's talk a little bit about the course organization
0:02 and how you're going to go through it during
0:04 your 100 Days of Code.
0:06 We don't have 100 separate little projects
0:09 nor do we have one huge project you work
0:11 on for 100 days.
0:14 Instead, we've broken the course into four day segments
0:16 where you work on one project, one idea
0:19 you learn one thing and you work on it
0:20 during those four days.
0:22 Typically, the way it goes is on the first day
0:24 you're going to watch the lessons.
0:26 They're usually 45 minutes to an hour
0:28 or maybe you do a little bit of coding
0:30 we'll tell you what to do and help you along the way there
0:32 but mostly the first day of any major topic
0:34 Django, Pyramid, Async, whatever
0:37 is going to be watching these videos.
0:39 Then then next day we're going to have some project for you.
0:42 And on GitHub, each section has its own read me
0:46 that says on day one or day N you do this
0:48 on day two you do that, on day three, day four
0:51 and it just walks you through.
0:52 It's pretty open-ended and you get to explore
0:54 and play with the ideas
0:56 but it is guided so you're not just left all alone.
0:59 Next day, probably a little bit more code
1:01 and then you might finalize what you're
1:03 working on and finish up that project as you go.
1:06 And that's typically a given topic in this course.
1:09 So you can think of this course as 25 four day segments.
1:13 Except, we've actually left one open
1:16 where we have four little independent ideas
1:17 that weren't big enough to fit into this format.
1:20 Also, some of the topics are longer
1:23 the way I've laid it out here.
1:24 For example, Docker is an hour and a half.
1:27 So on the first day, you watch maybe 50 minutes
1:30 of Docker, something like that.
1:31 Day two, you work on applying what you learned there.
1:34 Day three, you come back and watch some more videos
1:37 and build on that with, say, Docker Compose
1:39 in this example.
1:40 And then finally, on day N plus three or day four
1:43 you're going to finish up working with those new ideas.
1:46 So the basic workflow is these four day segments
1:49 on any given topic.
1:50 If you want to skip around, that's fine
1:52 that's totally okay
1:54 they don't have huge dependencies between them
1:56 but we do assume that you know what came before.
1:59 So, for example, if you jumped to the end
2:01 into some Flask section, we've assumed
2:04 that you have the knowledge that we covered
2:05 in the first part where we just introduced Flask
2:08 and things like that.
2:09 But as long as you're willing to fill in those gaps
2:11 or you feel like you have the prerequisite knowledge
2:13 you can jump around and that's okay
2:15 long as you think of this format
2:17 as being kind of the atomic unit there.