Welcome 🤗! In the next ~4h we will cover:

Mechanical Turk was a chess playing machine from 1770. You will solve a problem on a chess board later in Exercise 2.
Source
Before we begin with the class:
Midterm evaluation discussion three major quantitative (number) results:
Overall: Most students not satisfied. 30 of 54 (56%) disagree that course is good, compared with 9 (17%) who are satisfied and 15 in the middle.
Room for active participation: Slightly positive. 21 of 54 (39%) agree, 17 (31%) disagree.
Workload: The largest group says OK (21 students, 39%).
Three major qualitative negative points (from comments):
Insufficient foundational explanation
Some students expect more teaching (and less preparation).
Some students want less repetition of the book and more hands-on.
Students have different learning styles and I will not be able to hit everyone.
My style: I am convinced that a flipped class learning approach (Weekly class structure) prepares you best for the future and the knowledge you learn lasts longer.
Actions:
For less teaching people: I will pay attention that the test does not continue in the second hour.
For more teaching people: Until now, I don’t get any topics for just-in-time teaching . I will have a poll with explicit choices after the review activity.
Too steep a learning curve
Action: Coding from the first day instead of flowcharts next year.
I am open for other suggestions
Insufficient structure, clarity and quality control
Action: Quality control: I will send the content through the chat before publishing if I have reserve time
I am open for ideas for the other two points.
Too much obligatory expectations. The tests are here to give you weekly individual feedback, how you are doing.
Select one regarding the tests in 📊 Live poll:
We continue with the tests as they are.
We remove only the physical presence requirement for the tests.
We remove the physical presence requirement and extend the deadline (e.g., to at least 1-2 day/s)
We get rid of the test.
I don’t know / Something else.
Three major qualitative positive points (from comments):
TA’s support and individual feedback valued
Instructor’s engagement, friendliness, and responsiveness (to feedback)
Exercises, interaction, and peer support works well
Note: We get 4h/week per 60 students per rules. After last year’s feedback I asked for ~8h/week (2x) thanks to other courses which did not use their TA resources.
Other:
The homework will be released on mondays latest
As always, Feedback persons are welcome. If you want to be one, just speak with me before the lecture, I won’t ask again explicitly.
Test¶
(20 min)
Learning goals¶
Define and use an array
Use
size_ttype when iterating over an arrayInitialize an array
Differentiate between static and automatic arrays
Visualize variable modifications using step-by-step debugging
Pass arrays to functions
Preparation Review¶
E: Teach your peers¶
Question pool¶
Coding¶
If you are searching for a partner to work in a group, come to the front.
E: Array basics¶
E: Array processing order¶
E: Two dice sum statistics¶
E: Selection sort¶
E: Reflection¶
Let us revisit our learning goals:
Define and use an array
Use
size_ttype when iterating over an arrayInitialize an array
Differentiate between static and automatic arrays
Visualize variable modifications using step-by-step debugging
Pass arrays to functions
Do you still have muddy points?
![spices[4][9] instantiated in the kitchen of my sister. Wait, aren’t these rather 4 strings delimited by \0?](/_public/spices-from-sus-kitc-580faf19e970e60b70ad0561bf140147.jpg)
spices[4][9] instantiated in the kitchen of my sister. Wait, aren’t these rather 4 strings delimited by \0?