[TECH ED] Prepare for live session
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- express, javascript
- Domain
- documentation
Research direction
Open the linked Sprint 3 preparation coursework and work through the material before the Saturday session. Use the asking-questions guide for blockers; done means completing the preparation and bringing questions or misconceptions to the session.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://curriculum.codeyourfuture.io/servers/sprints/3/prep/
Why are we doing this?
It is essential to start learning new concepts and ideas before Saturday's session. During the week, we expect you to get stuck and form questions about the new content so you can address misconceptions during Saturday's session. The prep work here will introduce you to the new concepts for the week.
Maximum time in hours (Tech has max 16 per week total)
3
How to get help
Share your blockers in your class channel
https://curriculum.codeyourfuture.io/guides/asking-questions
Here's a suitable prompt for AI
Act as "Mitch", a straightforward and competent programming mentor. Use CEFR B1 English and always write in a simple modern functional programming style using es6. Walk me through the process of building a CRUD app with Express. I will paste you the code I have already, and then paste you a description of the next part I want to build. Don't write any code. Just walk me through a plan and prompt me as I write the code. Say "okee dokee" if you understand, and wait for my code.
Remember: AI is confidently wrong a lot. Always test its answers against documentation and write your own code.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeYourFuture/Module-Servers
-
π Priority Mandatory π Size Small π Servers π Week 2
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
CodeYourFuture/Module-Servers#21 Β·
-
π― Topic Problem-Solving π― Topic Programming Fundamentals π Priority Mandatory π Servers π Week 4 π¦ Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 45/100
CodeYourFuture/Module-Servers#142 Β·
-
π― Topic Problem-Solving π― Topic Testing π Priority Mandatory π Size Small π Servers π Week 1
CodeYourFuture/Module-Servers#141 Β· 1 assignee Β·
-
[TECH ED] APIs Open:brain: Prep work π― Topic Programming Fundamentals π― Topic Requirements π― Topic Teamwork π Priority Mandatory π Servers π Week 1 π¦ Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 35/100
CodeYourFuture/Module-Servers#140 Β·
-
[PD] Give feedback Openπ Priority Mandatory π Size Medium π Servers π Week 2
Difficulty 1/5 1-3 hours Newbie friendliness 35/100
CodeYourFuture/Module-Servers#139 Β·
All issues in CodeYourFuture/Module-Servers
Similar issues
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllTheMods/ATM-10-L#19 Β·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SignalK/n2k-signalk#345 Β·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
JuliaPluto/PlutoPlotly.jl#72 Β·