What helpers need to see
“It doesn’t work” is not a question. A good question includes: what you expected, what happened instead, the exact error text, the smallest code that still fails, and what you already tried. That package lets a human or a forum answer in one reply instead of twenty clarifications.
Shrink the code. Delete unrelated functions. Hard-code one input if you can. Share the language and how you run it. If the problem is on StudyGrid, say which lesson or lab. Do not paste secrets, passwords, or huge files.
Write the question as if you are helping tomorrow-you. Clarity is respect for other people’s time — and for your own.
A template you can copy
Goal: what should happen.
Actual: what happens (paste the error).
Minimal code: the shortest example.
Tried: two things that did not fix it.
Environment: language + where you run it.
Before you post, try reading the error and one more debug pass. Often the question answers itself — and when it does not, you still ask from higher ground.