About This is a sample application with basic functionality for the purposes of assessing technical candidates only. Do not be concerned if there is code in this application which is imperfect or insecure, just focus on the tasks provided in the Issues section of the Github repository. We expect the total time spent on the tasks in the Issues section not to exceed 3 hours; this is a suggested limit to respect your time, and we are not monitoring your time usage. Feel free to break up your time spent working on this as fits your schedule, there is no timer running ⏱ We understand that the use of codespaces may imply that we're monitoring your progress/time; in reality, we chose to use codespaces simply for the ease of ensuring a quick setup time and a uniform environment. It is not a deal-breaker if you do not get to everything. We do appreciate any and all context or psuedo-code for tasks which are incomplete, as that gives us a better understanding of how you would solve the problems presented if time allowed. Write your code as if you were a team member working on a joint codebase with other developers, following good team-based development practices. Assume your fellow teammates have not seen the project requirements. Test coverage is incredibly important to us, though as always, it is a work in progress. Follow campsite rules and leave things better than when you arrived. Assume you are writing this code for a production environment where errors and edge cases should be handled gracefully. Feel free to use Google and StackOverflow; after all, that is what we do every day in real-life programming. Feel free to do background research on a topic or library you encounter, and we hope that if nothing else, you are exposed to some new and interesting ideas through the process of completing this assessment. Later steps of the interview process may involve code review or pair programming in this project, so be prepared to explain your thought process. 🏗 Getting set up