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] Programmer Humour #207

Closed
kostiantynkovalchuk opened this issue Jan 14, 2025 · 1 comment
Closed

[TECH ED] Programmer Humour #207

kostiantynkovalchuk opened this issue Jan 14, 2025 · 1 comment

Comments

@kostiantynkovalchuk
Copy link
Owner

@SallyMcGrath cloned issue Migracode-Barcelona/Module-JS3#41 on 2024-07-05:

Link to the coursework

https://github.com/CodeYourFuture/Module-JS3/tree/main/programmer-humour

Why are we doing this?

We're making a very tiny application, the smallest one you can think of, that fetches from an API and shows something on a page. You should do this many times. Make ten more of these if you finish this early. Make it as simple as possible.

Remember: always do the simplest thing that can possibly work.

Maximum time in hours (Tech has max 16 per week total)

1

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 for this project called feature/xkcd

  3. Make regular small commits in this branch with clear messages.

  4. When you are ready, open a PR to the CYF repo, following the instructions in the PR template.

gitGraph

    commit id: "start"

    branch feature/xkcd

    commit id: "stub-files"

    commit id: "fetch-from-xkcd"

    commit id: "template-layout"

    commit id: "lighthouse-audit-revisions"

    checkout main

    merge feature/xkcd

Loading

There are several projects in this repo. Make a new branch for each project. This might feel challenging at first, so this is a good problem to bring to class to work on in groups with mentors.

Don't make one giant PR with all your work in for the module. Make a separate PR for each assignment.

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 once the coursework solutions are released.

@kostiantynkovalchuk
Copy link
Owner Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

1 participant