Put emails in the #refactor-track-tor channel for Harvest accounts
- Begin by making a list of all projects in your portfolio
- Prioritize your top 3 projects to improve or goals to hit
- Pull up the READMEs and the deployed application
- Write a quick summary of your concerns for the project (what you don't like, or what you want to learn)
- As you get your initial review done, drop a message in the #refactor-track-tor channel which should look like:
I would like to work on Project Name. Here is the link to the README and to the PRODUCTION SITE. I am concerned about how this project looks in responsive mode and bugs in my queries.
Meeka, Nathaniel and Bree will be walking around the room, responding to slack messages and giving advice.
- what red flags they would see in the project based on the production site or README
- help with prioritizing highest wins
- help with suggesting resources to study
- advice on workflow: example could be forking the repo or working from the original repo
Remember, a week feels like a lot of time but it really isn't. You want to start small.
While instructors are circling, complete the following activities:
- Clear out the issues in the repo that are no longer relevant or look unprofessional
- Document any bugs (look in responsive mode, try to break the app) as issues
- when you document the bugs, consider using recordit to snag gifs of the behavior and include the gifs in the issues
- Tag issues that you think are easy fixes
- In some document (however you manage your tasks)
- Pick out five goals (with links to issues) for the week that you can commit to making progress on.
- Document any questions or concerns with the project
- Write down any class refreshers that would be helpful to hit your goals
- example: I feel like my code formatting isn't great and I would like a refresher on how to hook up eslint in my editor
We will all gather together to make decisions on what classes will be held, our plans, and our concerns.