Online Programming Courses in Jeddah: How to Get Useful Feedback

Give the instructor a question they can investigate

Describe what the program should do, the smallest example that shows the problem, what it actually does and what you have already checked.

Replace “it does not work” with a testable question

Consider a fictional exercise: count the values strictly greater than ten. The input is 10, 11 and 15. The expected answer is two, but the learner's program returns three.

“My answer is wrong” provides little direction. A more useful question is: “The task says strictly greater than ten. With 10, 11 and 15 I expect two, but I get three. I think I may be including the boundary value. Could you help me inspect the condition?”

The revised question explains the requirement, supplies a small test and identifies a hypothesis. It still leaves work for the learner: inspecting the condition and explaining why the boundary should be excluded.

Send the smallest complete evidence needed

Use a short record rather than a long stream of unrelated screenshots. Include enough context to reproduce the issue, while removing material that cannot affect it.

If the program does not build, the diagnostic message may be more useful than an imagined runtime output. Include the relevant language and tool version when they could affect the issue. For a visual layout problem, a screenshot can complement a small HTML/CSS example, but it may not explain the underlying rules by itself.

Reduce the example without losing the problem

Work on a copy of the exercise. Remove unrelated features one at a time and check whether the same problem remains. If removing a piece makes the issue disappear, that is information worth recording rather than a reason to keep deleting blindly.

In the counting example, reduce a long list to the boundary value and two nearby values. Keep the rule “strictly greater” unchanged. Changing the requirement while reducing the input would make the comparison unreliable.

Use fictional sample values and remove passwords, personal records and private account details. Ask through the course's permitted support channel. If the question concerns assessed work, follow the course's rules about collaboration and the amount of assistance allowed.

Evaluate feedback by the reasoning it enables

A complete replacement solution may run, but you still need to understand the change. Ask which assumption was wrong, what observation supports the explanation and which test distinguishes the old behaviour from the corrected one.

For the example, the key question is whether ten itself is counted. A useful explanation directs attention to the difference between “greater than” and “greater than or equal to.” The learner should then choose or correct the condition and explain it in relation to the requirement.

Feedback can also say that the question lacks information. Respond by adding the missing input, message or instruction. Treat clarification as part of solving the issue, rather than interpreting every follow-up question as an unhelpful response.

Close the loop with your own tests

After making a reasoned change, try cases that isolate the rule: 9 should not count, 10 should not count and 11 should count. Then return to the original three-value example and confirm the result is two.

Write a short note: “I included the boundary although the task excluded it. I changed the condition and checked values below, at and above the boundary.” Later, solve a similar task independently with a different threshold.

This final attempt helps distinguish understanding from copying a correction. If the new task still causes confusion, bring the specific difference back to the instructor.

Ask about feedback before choosing a course

When comparing online programming courses available to learners in Jeddah, ask how questions are submitted, whether exercises receive individual review and whether there is an opportunity to retry after feedback. Confirm any stated response arrangements directly with the provider.

A sample exchange can show more than the word “support.” Look for feedback that refers to the learner's evidence and gives a clear next action. Use the same standard when preparing your own questions: make the issue understandable, then take responsibility for explaining and testing the improvement.