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

[TECH ED] Module Project Level 100 #61

Open
HarounAlarabi opened this issue Aug 7, 2023 · 0 comments
Open

[TECH ED] Module Project Level 100 #61

HarounAlarabi opened this issue Aug 7, 2023 · 0 comments

Comments

@HarounAlarabi
Copy link
Owner

From Module-Databases created by SallyMcGrath: CodeYourFuture/Module-Databases#1

Link to the coursework

https://github.com/CodeYourFuture/Full-Stack-Project-Assessment

Why are we doing this?

Here is the fabled Full Stack Assessment. This project will help you prepare for Final Projects. You must reach level 100 this week, but you can progress as much as you like.

Make sure you complete each level before moving on to the next stage. Your project can only be assessed as reaching a level when all the requirements for that level are met. When you get stuck, open a PR and explain your blocker. Get help from colleagues and mentors.

As a professional developer, you will often encounter blockers in your daily work. It can feel frustrating. Learning to share your blockers productively and resolve them collaboratively is an important step in becoming a good developer.

https://github.com/CodeYourFuture/Full-Stack-Project-Assessment

Maximum time in hours

6

How to get help

Share your blockers in your class channel. Use the opportunity to refine your skill in Asking Questions like a developer.

How to submit

  1. Fork to your Github account.
  2. Make a branch called Level 100
  3. Make regular small commits to your branch with clear messages.
  4. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.

How to review

  1. Complete your PR template
  2. Ask for review from a classmate or mentor
  3. Make changes based on their feedback
  4. Review and refactor again next week

Anything else?

Final Projects Entry and Exit Criteria

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment