Non-trivial tweaks to Data Flows sprints 2 and 3

[illicitonion]

What does this change?

As well as a bunch of copy edits, a few non-trivial changes:

• Sprint 2's code didn't actually fully work in a bunch of ways. Add soem blocks and steps making sure we actually step through all the issues that come across in the code we're teaching. I'm consciously leaving this mostly as a worked example, rather than do-yourself exercises, because the trainees already have the TV Show project as an entire do-yourself exercise about the same topics.
• When working with promises, consistently tell people to save examples to files and run them, rather than run them in the repl. This is because if you execute these snippets in a repl you get printed out extra Promise values (because the repl prints out each evaluated expression), which makes it much harder to do things like "spot the difference between what returns a promise and what evaluates to a value").
• Completely remove Promise.catch This is probably the most controversial but I think it's important. Two main reasons:
  1. We haven't actually taught try-catch anywhere, so we can't just rely on transferring "it's the same as you already know, just async".
  2. There are already way too many novel concepts in Data Flows Sprint 3, and it's already very hard to follow from scratch. If we add try-catch earlier in the course (which I think we should), we should re-add this.

Common Content?

Yes. Much of js3. Including adding new blocks.

Org Content?

Yes - Data Flows sprints 2 and 3 prep, and sprint success.

Checklist

• [x] I have read the contributing guidelines
• [x] I have checked my spelling and grammar with an automated tool
• [x] I have previewed my changes to check the markdown renders as I intend
• [x] I have run my code to check it works
• [x] My changes follow our Style Guide

[netlify[bot]]

✅ Deploy Preview for cyf-programming ready!

Name	Link
🔨 Latest commit	eeac7354fabf091e7d80f6eb96858848fd853d68
🔍 Latest deploy log	https://app.netlify.com/sites/cyf-programming/deploys/671ab676a5a3590008c87a0b
😎 Deploy Preview	https://deploy-preview-1111--cyf-programming.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (🟢 up 15 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 90 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify[bot]]

✅ Deploy Preview for cyf-curriculum canceled.

Name	Link
🔨 Latest commit	eeac7354fabf091e7d80f6eb96858848fd853d68
🔍 Latest deploy log	https://app.netlify.com/sites/cyf-curriculum/deploys/671ab6760f44bb0008b68dd8

[netlify[bot]]

✅ Deploy Preview for cyf-common canceled.

Name	Link
🔨 Latest commit	eeac7354fabf091e7d80f6eb96858848fd853d68
🔍 Latest deploy log	https://app.netlify.com/sites/cyf-common/deploys/671ab6766b50e8000871d88c

[netlify[bot]]

✅ Deploy Preview for cyf-piscine ready!

Name	Link
🔨 Latest commit	eeac7354fabf091e7d80f6eb96858848fd853d68
🔍 Latest deploy log	https://app.netlify.com/sites/cyf-piscine/deploys/671ab676dc5fd700085b2aa8
😎 Deploy Preview	https://deploy-preview-1111--cyf-piscine.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 96 (🔴 down 3 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify[bot]]

✅ Deploy Preview for cyf-launch ready!

Name	Link
🔨 Latest commit	eeac7354fabf091e7d80f6eb96858848fd853d68
🔍 Latest deploy log	https://app.netlify.com/sites/cyf-launch/deploys/671ab676167fbc0008963989
😎 Deploy Preview	https://deploy-preview-1111--cyf-launch.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify[bot]]

✅ Deploy Preview for cyf-tracks ready!

Name	Link
🔨 Latest commit	eeac7354fabf091e7d80f6eb96858848fd853d68
🔍 Latest deploy log	https://app.netlify.com/sites/cyf-tracks/deploys/671ab676859a160008eed317
😎 Deploy Preview	https://deploy-preview-1111--cyf-tracks.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify[bot]]

✅ Deploy Preview for cyf-itd canceled.

Name	Link
🔨 Latest commit	eeac7354fabf091e7d80f6eb96858848fd853d68
🔍 Latest deploy log	https://app.netlify.com/sites/cyf-itd/deploys/671ab676504491000864f8f5

[netlify[bot]]

✅ Deploy Preview for cyf-sdc ready!

Name	Link
🔨 Latest commit	eeac7354fabf091e7d80f6eb96858848fd853d68
🔍 Latest deploy log	https://app.netlify.com/sites/cyf-sdc/deploys/671ab676895f16000830ac7b
😎 Deploy Preview	https://deploy-preview-1111--cyf-sdc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[illicitonion]

General "read vs do" approach

I definitely struggle with the balance between provoking learners to do things for themself and also explain things to make sure they're not lost and also be able to foresee issues they may run into. Would love to discuss general strategies here!

Videos

I think probably videos are the place for exposing and resolving roadblocks, not more text.

I'm not sure I agree videos are the place for this. I think interactive sessions are.

Videos can be great alternate ways of presenting information, but I don't think are typically great ways of clarifying misunderstandings.

I can't speak for anyone else, but for me I don't typically learn much from watching someone not understanding something and then have a conversation helping them understand it. I learn from raising my own misunderstandings and having them actively resolved, or from watching other people in a dialogue and being able to chip in my own issues.

Watching someone else's recoded session of this, I:

1. Struggle to focus
2. Get bored by people debugging an issue I do understand so stop paying attention
3. Maybe don't get my own misunderstandings addressed at all
4. If they are addressed, maybe the explanations don't land with me

I think providing videos of this process is better than not doing so. But for me the real value we should be offering is sessions with people who do understand (either on Saturdays, or in the week) to interact with live.

I don't think the goal of Mitch's videos was to replace these discussions, though they do serve as an "in case of emergency" backstop in case there are no volunteers around. In my idea world, learners would be able to read the material, do the exercises, and get help when they need. I think this was what Mitch was offering in the sessions when they were being filmed, and we should be wary how extensively we re-purpose them.

[SallyMcGrath]

I agree they shouldn't replace discussions, but they should replace long divergence into common problems the learner will encounter. With timestamped chapters, this can really help resolve blockers outside of class day.

I think we both need to valorise videos a bit BECAUSE we both hate them. Trainees love them (not all, but many). It's the most consistent feedback -- more videos, more videos, they love the videos.

I can't pay attention to a video for more than a minute or so. I can't remember anything anyone says to me either! I never learn anything in a workshop or training session. I like to read some long clear narratives, sketch out the model that's built in my head, build some code to apply it, and fill in the gaps with docs. That's my preference, massively. But it's not at all common, and if it's just you and me we will trend text heavy (with some pictures from me).

Length and anticipatory explanation are your main risks. Abstraction and analogy are mine.

I think we need to keep the video-loving needs of other learners in view.