Do they save the captcha result in a localstorage or the session cookie and avoid checking again? I also think having sequential number for student Ids is not a good idea. IDs should be random unique values in my opinion. But if this is sort of essential, then they can add an extra form input like last name or DOB or even a secure pin digit for each student.

Best documentation I've seen:
- Hasura docs
- Gatsby
- Netlify

Worst documentation I've seen:
- Google gsuite, API, addon docs (everything is spread over a lot of different documentation locations, u need to read 4 websites to understand the whole details u need, some of the critical information is in support answer urls).

-AWS documentation for some services, not all services (also sometimes spread over few urls, some old, some new; some of the wordings feels like I need a masters degree in English to decipher the real intent of the author; feels like some docs are written in a rush).

Writing a well documented read me file with how to actually build the app will gain you some positive points from your team. You can approach this backend person and tell them, "since there is no readme file, and I might end up asking a lot of questions, why don't we go together through building the whole app, and I can document the process to add it to the non-existent README file. I will also add all my relevant questions in a faq section too".

This would go a long way for any future developers joining this project.

In my team, everytime we have someone new join the team, we ask them to ask as many questions and build the app themselves using the existing readme, and whatever they get stuck on, they need to update it. This helped in keeping an updated readme that works across different devices and also avoided the bias of existing team members.