Send the brief
Share the brief, deadline and relevant files.
Send your current work; the next step is to identify the exact concept, bug or documentation problem blocking your progress.
Share the brief, deadline and relevant files.
Describe what you tried and what is not working.
Clarify the topic, tool, language or concept involved.
Investigate small test cases, code sections or assumptions.
Understand why an approach works or fails.
Check tests, documentation and required files again.
“My code does not work” is a start. More useful is: “For input X I expect Y but get Z, and the problem started after change A.” That makes debugging and technical explanations much more efficient.
You do not need to write a long explanation. A few concrete details are enough to show whether the problem is about theory, programming, data, networks, security, tools or documentation.
For example algorithms, Java, databases, cloud computing or cyber security.
The relevant section or a readable screenshot is enough for an initial review.
Which parts already work and which files or results do you have?
Exact error message, wrong output or an example that triggers the problem.
What did you expect to happen instead?
When is the assignment, report or project due?