---
tags: Documents
---
# What to do 15 Minutes Before getting Claimed on SignMeUp

:::warning
Obsolete. This has been integrated into the Hours Guide.
:::

<style type="text/css">
ul { list-style-type: lower-alpha; }
</style>

1. Make sure you have a specific question ready. The more specific you are, the easier it is for TAs to guide you or help you locate your bug faster!
2. Reread the assignment. Sometimes one overlooked detail can make the difference between a complete solution and a broken one! Remember to keep the end goal in mind as you write up your answer.
3. If you need help debugging:
* Follow this [guide]() to help you locate the issue and potentially fix your issue!
* Identify what tests are failing and let your TA know so they know what the issue is
* Comment out the sections of your code that aren’t relevant to your issue!
* Rename your variables! Only do this if your variable names don’t hint at what that variable is used for. This reduces the effort needed to read and understand your code
* This goes without saying, write tests!
4. If you need help conceptually:
* Jot down some examples for the function and their expected output.
* Walk through your examples and how the function should handle these inputs after every successive recursive call or iteration.
* Identify which examples you weren’t sure how the function should handle them and let your TA know.
* If you couldn’t walk through an example completely or got stuck with how the function should approach that kind of example, that’s fine! Let your TA know!
5. Be ready to join the meeting room. This minimizes downtime and lets us meet with as many students as possible.
6. Check piazza! There’s a good chance someone has already asked the same question as you.