Production applications
Full-stack web and mobile, taken to something you can maintain after I leave.
How I approach it
A surprising share of this work begins with a repository somebody else left behind. Both of my recent contracts did. The first task is not to build anything — it is to say plainly what runs, what does not, and what is worth keeping.
That assessment is worth paying for on its own. Deciding to rewrite something that mostly works, or to build on something that fundamentally does not, is the expensive mistake, and it is usually made before anyone writes a line of code.
Handover is part of the build rather than an afterthought at the end. If your team cannot maintain the system without me, the engagement has not actually finished.
What this covers
- Next.js and React front ends; React Native across iOS and Android
- Python, FastAPI, and Node back ends with the data model thought through first
- Inherited codebases: assessment, then a plan, then the work
- Handover that includes documentation, not just repository access
What you get
- Work landing in your repository in reviewable pieces, not one reveal at the end
- A written assessment first, where a codebase is inherited
- Documentation and, where the software has operators, a guide written for them
- A walkthrough at handover, and code you own outright
Relevant work
Other services
Need this on a project?
Describe what you are building and where it is stuck. The scoping call costs nothing, and you get a written scope and price before any work starts.