As of mid-2020, I changed the way I develop new university courses. I found out that it motivates me to develop material for lecture slides by following a blog post mindset. As a connoisseur of open access, open data, and openness in general, I will make the material openly available on my website. These posts will be called drafts and have a corresponding category.
A draft is a document that has several characteristics:
- A draft is topic-oriented. I might use a draft as is for building a topic for a lecture. I might use a draft vertically to build several lectures. Drafts do not follow any logical order of appearance.
- A draft reflects work in progress. Once some note for a topic within a lecture reaches a sufficient state, I turn it into a draft. Drafts have typos. Drafts might have weird language.
- A draft is for me to successively build a lecture. A draft is not a lecture. A draft by itself will never turn into a lecture.
- A draft lacks context. By reading a draft, you might think that it lacks important background topics. It might be an oversight on my side, but it might also be by design (example: a course on full stack web development will include some topics on computer networks but will ignore many of them, as well).
- A draft calls for feedback. If you read a draft and notice something erroneous or missing, feel free to offer your feedback. I welcome it! Either contact me or comment below it.
- A draft is to help. I am sharing this material with the hope that it helps visitors who want to know about and my students who might use it as a script for a course.