Research & scientific computing
Analysis pipelines and research tooling, from someone who has also been the researcher.
How I approach it
I am a published researcher as well as an engineer, which mostly means I know what a reviewer will ask. Software written for a study has to survive that question: can somebody else reproduce this months from now, from what is written down?
Measurement by eye is slow and hard to defend. Replacing it with tooling that is consistent between samples and reproducible by a different person is usually where the value is.
Grant timelines and academic collaboration are familiar rather than novel, including the parts that are not code — the reporting, the figure preparation, and the methods section that has to describe what the software actually did.
What this covers
- Bioinformatics pipelines and gene expression analysis
- Image analysis software for laboratory workflows
- Statistical modelling, visualisation, and reproducible analysis
- Grant-funded timelines and academic collaboration
What you get
- Analysis that reproduces from a clean checkout
- Figures prepared to publication standard
- A methods description accurate enough to submit
- Tooling your group can run without me
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.