Break closures into its own segment

[djmitche]

In teaching the course last week, we broke here, partly due to time constraints, but partly because this is a pretty mind-bending topic to tackle at the end of an information-dense day. A break helps, and spreading the content over a few slides helps as well.

By the timings in the course, this leaves day 2 looking like

Fundamentals // Day 2 Morning
1 hour and 55 minutes: (1 hour and 10 minutes short)

• Welcome - 3 minutes
• Pattern Matching - 45 minutes
• Methods and Traits - 50 minutes

Fundamentals // Day 2 Afternoon
3 hours and 30 minutes (⏰ 30 minutes too long)

• Welcome - 0 minutes
• Generics - 45 minutes
• Standard Library Types - 1 hour
• Standard Library Traits - 1 hour
• Closures - 20 minutes

Maybe we should move generics to the morning session?

[hurryabit]

Should we move generics into the morning session?

[djmitche]

Uh, I asked first :)

[fw-immunant]

As a data point, when teaching I usually end up breaking after standard library types (which is quite a slog, because I do think it worthwhile to dig into the particular APIs provided by collection types, but it can get a bit dry) and before standard library traits.

[hurryabit]

Generics in the morning session look nice. Thanks.

[djmitche]

As a data point, when teaching I usually end up breaking after standard library types (which is quite a slog, because I do think it worthwhile to dig into the particular APIs provided by collection types, but it can get a bit dry) and before standard library traits.

The design is to break between each segment, so that is an expected break :)