About

A chemist who learned to compute.

I read Medicinal Chemistry at Cardiff University, spent three years doing the laboratory work that teaches you what a molecule actually is, and then started building the computational skills to work on biological questions at a scale the bench cannot reach. I am not leaving chemistry behind — it is the thing that makes the computational work worth trusting.

Education

The foundation.

2022 – 2025

2:1

BSc Medicinal Chemistry · Cardiff University

A chemistry degree oriented towards drug design: how molecules are made, how they are characterised, and how structure governs the way they interact with biological targets.

Medicinal chemistry and molecular design Organic and inorganic chemistry Physical and analytical chemistry Molecular interactions Chemical characterisation Computational chemistry Biological and pharmaceutical principles
On the 2:1. It is what it is, and I would rather state it plainly than bury it. What I would ask anyone assessing me to weigh alongside it is the work on this site: it is independent, it is documented, and it can be checked.
Undergraduate research · 40 credits

Catalytic synthesis of a biobased heterocyclic scaffold.

An independent research project spanning synthesis, catalysis, analytical characterisation and molecular docking — which is also, in miniature, the arc this whole portfolio follows.

Select a stage to read what it involved and why it mattered. Stages and techniques only — results are in the dissertation itself.

01 Motivation

Furfural is derived from agricultural residues rather than petrochemical feedstock, which makes it an attractive starting point for building heterocyclic scaffolds. Heterocycles are everywhere in medicinal chemistry: they provide the rigid cores and hydrogen-bonding patterns that let a small molecule present a defined shape to a protein. The project asked whether a biobased route could deliver a scaffold of genuine medicinal interest.

02 Reaction design and catalysis

The synthetic work compared heterogeneous catalysts — Amberlyst-26, γ-alumina and calcium oxide — for the key transformation. Heterogeneous catalysts are chosen partly for practical reasons: they can be recovered and reused, and they avoid contaminating the product with residual metal. Comparing an ion-exchange resin against two metal oxides meant comparing quite different surface chemistry, and so quite different behaviour in the same reaction.

Why this matters computationally. Catalyst comparison is an experiment with a small number of expensive runs, which is the opposite of the data regime I now work in. Having done both, I have a reasonably concrete sense of what experimental data actually costs to produce — which changes how you treat a public dataset of ten thousand samples.

03 Analytical characterisation

Thermogravimetric analysis, transmission electron microscopy and gas chromatography were used to characterise the catalysts and the reaction outputs. Each answers a different question: TGA on thermal stability and loss of volatiles, TEM on morphology and particle structure, GC on what the reaction mixture actually contains.

The habit this builds is corroboration. No single technique establishes a result on its own, and when two disagree the disagreement is the finding. That transfers directly: a differential expression result and a pathway enrichment result that point in different directions are telling you something, and the temptation to report only the one that fits the story is exactly the thing to resist.

04 Molecular docking

The computational component investigated how the synthesised scaffold might bind a protein target, examining poses and the interactions available to the ligand within the binding site.

The limitation I would state first. Docking scores rank poses within a scoring function. They are not binding affinities, they are not validated predictions of activity, and the correlation between docking score and measured affinity is frequently poor. The honest claim is that docking generated a structural hypothesis about how the scaffold could sit in the site. Confirming it would require experimental binding data.

05 What it taught me

Three things, all of which show up in the computational work on this site.

  • Molecules are physical objects. When a model outputs a logP or a descriptor vector, I have some intuition for whether the number is plausible, because I have handled compounds whose behaviour those numbers are trying to describe.
  • Characterisation is adversarial. You run several techniques because you are trying to catch yourself being wrong, not to accumulate supporting evidence.
  • Computational output needs a stated epistemic status. A docking pose is a hypothesis. A SIFT prediction is a hypothesis. Treating either as a finding is the most common way computational work loses credibility with experimentalists.
The transition

Not a change of direction. A continuation.

The route from experimental medicinal chemistry to computational biology is shorter than it looks. Both are about structure determining behaviour; the difference is scale and the kind of evidence available.

  • Molecules → targets. Medicinal chemistry asks how one molecule engages one protein. Pharmacogenomics asks what happens when the protein varies between people.
  • Targets → systems. A drug–gene pair is one edge in a much larger graph. Network and pathway analysis is the same question asked of the whole system.
  • Systems → populations. Allele frequencies and association statistics ask how that variation is distributed, and what follows for treating people rather than samples.
  • Throughout → engineering. None of it is useful if it cannot be re-run. That is why the software work is on this site rather than hidden in a footnote.

Beyond the science

Alongside the research work I build and run Gradify, a family of learning platforms, and ForgeLab, a browser-based code execution and grading system. They are products rather than research, but they are where most of my software engineering has actually been learned: schema design, sandboxing untrusted code, automated testing and shipping things other people depend on.