Debugging & Code Review
Fixing code that will not run, and reviewing code that runs but should not be trusted.
Explore
Technical & Programming
Technical Documentation
READMEs, API references, architecture notes and user guides written for the person who has to use them.
Documentation is written for someone who does not already know how the system works. That sounds obvious and is almost never how it is actually written.
We document the decisions and the failure modes, not only the happy path — which is what a reader usually needs at the moment they open the document.
What you receive
- README with setup instructions verified on a clean machine
- API reference or OpenAPI specification
- Architecture overview with a diagram
- Troubleshooting section covering real failure cases
Related
Others in Technical & Programming
Git, GitHub & Version Control
Setting up version control properly, and rescuing repositories that have gone wrong.
Explore
AI & Machine Learning Implementation
Model development, fine-tuning, retrieval-augmented generation and getting a model out of the notebook and into use.
Explore
MS Project & Primavera P6
Work breakdown structures, critical path, resource levelling and baselines for construction and engineering projects.
Explore
Next step
Ready to talk about Technical Documentation?
Send the brief, the deadline and anything you already have. You will get a reference number straight away and a considered reply, usually within one working day.
- Fixed quote agreed before any work begins
- A reference number you can quote on WhatsApp
- Confidential handling, and an NDA if you want one
- An honest answer if your deadline is not realistic
