Send the Part of Your Computer Science Assignment You Are Stuck On
A short description plus the brief, code or error message is enough for the first contact.
What to send
- module or subject
- brief or screenshot
- deadline
- existing code / notebook / configuration
- exact error message
- what you have already tried
“Java module, due Friday. My program reads the CSV file but throws a NullPointerException when a value is empty. I have attached the relevant code and the error message.”
That description is more useful than simply “Java does not work” because the behaviour that needs investigation is clear.
The first step is to identify the problem rather than send a generic answer
After your message, the goal is to identify whether you need concept help, programming support, debugging, testing or documentation guidance. If context is missing, the assignment brief, relevant file and exact error message are usually the most useful additions.
For larger projects, mark the problematic part first. There is no need to explain the entire repository if only one component or test is causing the issue.