-
-
Notifications
You must be signed in to change notification settings - Fork 133
Blog post about splitting the bc
repository
#610
Conversation
Each topic within a lesson should explicitly say how long it should take to teach. |
Each topic within a lesson should explicitly say how long it should take to teach. Isn't that quite hard to say? It may very a lot between audiences... |
Average and std deviation?
|
I would say the time for each lesson should be used as a guideline if instructors plan to take things in/out of the lesson. Yes it would vary depending on the audience, but other than git, the the responses I have been collecting have been about the same [1]. [1] if you drop the extreme observation of teaching all of git in 1 hour, then git would also be about the same from the data I've collected. |
I'd be happy with an estimate from the lesson's author, and additions |
than what we currently have. | ||
As a fringe benefit, | ||
people will be able to subscribe to only the ones they care about most, | ||
so that they aren't flooded with comment and commit messages on topics they're less interestd in. |
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.
Typo: "interestd"
Blog post about splitting the `bc` repository
This blog post outlines plans for breaking up the
bc
repo into smaller, more manageable pieces.Please put comments about lesson templates, the mechanics of moving content over from the old repo, etc., on this issue in the
bc
repo.