Skip to content
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

Week 3 QA content #462

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

tomasvanrijsse
Copy link
Contributor

I ran this QA with two exercises

  1. Do normalization together
  2. Build a small API using MongoDB

Copy link
Contributor

@unmeshvrije unmeshvrije left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see no harm in keeping mongodb/create-employees.js
This file has a minimalistic example of how mongodb client can be used via JS.

I like the idea of giving students the boilerplate for TODO-server backend! Great addition 👍

Normalization exercises need some revision because I don't understand the rationale behind it. Perhaps if I know your vision, then I can come to appreciate it better. Let me know if you want to talk about it.

Week3/normalization exercise/README.md Outdated Show resolved Hide resolved
Week3/normalization exercise/README.md Outdated Show resolved Hide resolved
Week3/normalization exercise/realistic exercise.md Outdated Show resolved Hide resolved

const collection = await getMongoCollection();

// http://mongodb.github.io/node-mongodb-native/3.6/tutorials/crud/#read-methods
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose students are supposed to fill some working code here.

@tomasvanrijsse
Copy link
Contributor Author

I could have put in some more explanation I see 😄

I used the Normalization exercise content live, so I share my screen and show them the files.
These two files are like my slides 😋 but I didn't know how to store my slides in git properly.
The readme.md is my first slide, and it's purpose is to appeal to their sense of "are we ever going to need this?".
Then in the second file is to demonstrate that the subject is useful eventhough it feels unnatural.
https://youtu.be/z6DMh2Ob9d0?t=73

@unmeshvrije
Copy link
Contributor

I could have put in some more explanation I see 😄

I used the Normalization exercise content live, so I share my screen and show them the files.
These two files are like my slides 😋 but I didn't know how to store my slides in git properly.
The readme.md is my first slide, and it's purpose is to appeal to their sense of "are we ever going to need this?".
Then in the second file is to demonstrate that the subject is useful eventhough it feels unnatural.
https://youtu.be/z6DMh2Ob9d0?t=73

I think adding explanations for all steps makes sense because if another mentor picks up the module to teach then (s)he would want to conduct the same demonstrations as you did. And I think they are quite helpful.

It would be nice if you have answer some other questions and resolve those conversations on this PR

restore delete mongo example


change the readme
@tomasvanrijsse
Copy link
Contributor Author

I removed the normalization exercise and squashed some commits from the MongoDB express server backend.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants