This repository contains my entries for the April/May Chingu FCC Speedrun Challenge.
To fork a copy of your own and participate, there's a clean repo you can fork here: Chingu FCC Speedrun Challenge
The golang / react variation is just something I'm doing, most people will be using the typical FreeCodeCamp stack (Node.js, Express, MongoDB, and Angular or React). I'm going a bit outside the box regarding my stack because I participated in a previous challenge with the typical stack and want to push myself a bit to learn some new technologies.
Fork this repository and add your code for each project to the appropriate folder in your repository as you complete each project.
You may work in pairs for phase 1 and you and your pair may share the same repository for phase 1. For phase 2, each participant should create a new repository to contain their personal Portfolio SPA.
Complete as many of the FCC Projects as you can in a three week period.
To prepare for Phase 2 you'll want to ensure that you use the same "stack" and keep to a consistent coding style across projects.
Time limit: three weeks
Integrate all of the FCC Projects you created in Phase 1 into one comprehensive single page portfolio application.
Time limit: one week
Deadline to complete both Phases:
Current challenge - Countdown Clock
Original challenge - Completed in March 2017 - Countdown Clock
- Pick one stack and stick to it (it'll make Phase 2 easier). Any stack is fine, but stick to just one.
- You may reuse code you previously wrote, but try to improve on your prior effort in some way.
- You may work in pairs for Phase 1 and contribute to a shared repository for Phase 1.
- Each individual must complete Phase 2 solo, in their own repository.
- For each project in Phase 1, each participant must write their own blog post about their experience working on that project. This can be on your own blog, Medium, wherever and can contain whatever you want: a brief blog style ramble about how you felt during the project, a tutorial explaining some concept you learned during the project, a series of photos showing your cat sleeping on your desk while you worked on the project - whatever - but something.
- All code for Phase 1 should be committed to your fork of this repo.
- Phase 2 code should be in a separate repository each participant creates to contain their personal Portfolio SPA.
- You may ask for help and help others - preference should always be given to helping someone understand, not handing them code they don't.
- If someone is stuck, you may pair with them to help them get unstuck (on as many projects as you want) even if you're doing your own entry separately or with another pair.
- If someone pairs with you to help you get unstuck, be sure to make a note to credit them in your repo and in your blog posts.
- For Phase 1, all of your code should be committed/pushed to the appropriate directories in your fork of this repository.
- For Phase 1, you do NOT need to host the projects on a live site, merely test them locally, then commit your code. You can, of course, host a demo of the project if you want to though.
- For Phase 1, you must write a blog post for each project you complete and link to it in the projects table (in your fork of) this README file.
- For Phase 2, you must each create a repository to hold your individual Phase 2 project, then link to that project in the portfolio/README.md file of this project.
- For Phase 2, you must both commit your code to github, and host a live version of your project.
Who can complete the most projects in Phase 1?
Who can make the most complete and professional looking portfolio in Phase 2?
Note: This is the type of competition where, yes, winning is awesome, but participating and giving it your all is the best prize, and everyone can get that :D
Copy this table as needed to make a separate table for each team member for recording blog posts