-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add JS3 Week 2 prep content MOVED TO SPRINT 3 #403
Conversation
✅ Deploy Preview for cyf-curriculum ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Thanks! I'll take it from here @Dedekind561 . Hands off the keyboard! See you tomorrow! |
I think that's all we can reasonably do. I feel overloaded just writing it. Next week we can do sequencing, async/await etc
OK so I've reordered it and split it into two pieces as per #315 This week considers asynchronous execution in a single threaded language.
I have drawn a crazy map. I actually find sketching like this amazingly helpful and I know some trainees do too. But I have hidden the large ones behind details blocks as I don't want to break people. If you would like to improve this map, I recommend this live editor for Mermaid |
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.
Generally looks good - I opened up #462 with some copy edits.
I'm not sure I'm sold on the "using promises without explaining promises at all" part... I'd maybe be tempted to remove the .then
and "console.log
a promise and look at it" piece, and just give the replacement code and say "We'll learn more about how it works next sprint"... WDYT?
Copy edits to JS3W3
1. update time of async 2. move blocks into en 3. clarify web api def 4. bold latency 5. clarify concept list 6. rm unused blocks
it should be a web component
skip straight to film fetch
autocomplete strikes again
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.
the ultimate fix for this will clearly be to write some kind of mutation observer in here
What does this change?
Module:
Week(s):
Checklist
Description
Who needs to know about this?