Start with the system and the problem
Email a concise description of the application, what is happening, and what needs to be true when the work is complete. Relevant links, logs, screenshots, and constraints are useful context.
How it works
A clear path from an unknown issue to a usable handover.
Existing systems need careful context before they need code. The process keeps the work tied to the business outcome and makes each next step visible.
Assess the technical path
I review the available evidence, identify the access and context needed, and clarify the likely scope. If the work is a fit, you receive a focused proposal for the next piece of work rather than vague capacity.
Make, verify, and explain the change
Agreed work is implemented against the existing system, tested in the appropriate environment, and prepared for deployment. The handover documents what changed, how it was checked, and any remaining risks or follow-up work.
Working style
Designed for practical decisions
The aim is to replace uncertainty with an understandable technical path. That means clear scope, evidence-based decisions, tested changes, and documentation useful to the people who will operate the system next.