This project appeared to be some sort of app that volunteers log into, to track appointments with clients. I'm not sure
what the problem domain is, but the functionality was pretty simple.

Jumping into the code base was actually pretty easy. We paired on solving this problem by talking about routing, what was
served up, and then finding what front end component we needed to work on. The setup was clear but we ran into problems at
first. I followed the directions, but missed one crucial step. I had to run rails server while running a couple of yarn commands,
which generated the front end code. This was very different from setting up other projects, so it wasn't immediately clear
that I had done something incorrectly. Lastly, the code base was different that how I would approach it. I don't think the
controllers were very restful, and there was some stuff going on in there that I would do, but that is a minor gripe.

The real problem with the codebase, was the React component. There was a single file with a ton of different components, all
in one file. Then there was the logic that was being done in the render views for React. This made it really hard to follow.
Other than that, we were able to resolve the issue and make a pull request.

The issue was that a volunteer needed to be notified of a client's out of date or non-existant USDA certification. They would
then need to sign a new form. So we built a component that checked the props data for a client, and then made a validation
and rendered the view if the cert was invalid.