# support · support.log
Code Review & Fixes
Your own code, reviewed and fixed — not rewritten from scratch behind your back.
Sometimes the work is 90% there and just needs a second pair of eyes before submission — not a rewrite that makes it unrecognisable as yours. We review what you've built, fix what's actually wrong, and explain every change so you can talk about your own code with confidence, because it's still your code.
What you get
- Review comments explaining what's wrong and why, not just a diff
- Fixes applied to your existing structure, not a rewrite
- Style kept consistent with what you already had
- A short list of the changes made, for your own record
- Flags on anything a marker is likely to question, even if it "works"
- Available for a follow-up call to walk through the changes
What to send first
- Your repository or a zip of the current code
- The exact error message or failing test, and the steps to reproduce it
- What you have already tried
- Your viva or submission date, if there is one
How it runs
- 01
Send the spec
The brief, the rubric, any starter code and the versions your marker uses. A photo of the PDF is fine to begin with.
- 02
Scope and quote in writing
We read it properly, ask what is unclear, and confirm a fixed price and delivery date. A small advance confirms the order.
- 03
Build against the brief
Work is tracked task by task against the spec. Longer projects are split into milestones you can review as they land.
- 04
Tested handover
A repo that installs from a README, run against your test cases, with the write-up if your rubric asks for one.
- 05
Fixes and walkthrough
One round of fixes if a marker flags something, and a walkthrough of how it works so you can explain it.
Code Review & Fixes: common questions
Yes, and that is usually better for you — we keep your structure and style, fix what is broken and explain each change so you can talk about it.
A screen-shared call on Google Meet or Zoom at a time you book. You drive, we diagnose, and you end the call with working code and a note of what caused the problem.
It depends on the scope of the brief, the stack and the deadline. Send the spec on WhatsApp and you get a fixed price and delivery date in writing before any work starts — no hourly meter.
Turnaround depends on scope and is agreed with the quote. Tell us the real deadline, including the timezone, and we will say honestly whether it is workable before you commit.
// related
Often paired with code review & fixes
Live Debugging Sessions
Live debugging on a call — the bug found and explained, not just silently patched.
support.logUnit Testing & QA
Test suites written to your framework, covering the cases a marker will actually try.
support.logGit & Version Control
Git history and workflow set up properly, for a submission that's judged on commits too.
./send-brief
Send your code.
Paste the code review & fixes brief into WhatsApp — the message already names the service. Scope and price come back in writing.