Some thoughts on AI and where science might be headed
Why AI may change science first through the operation of research rather than through a single decisive prediction.
Scientific Software and Platform Specialist
I work where scientific ideas, software engineering, data workflows and AI-enabled R&D meet.
My focus is turning complex scientific capability into dependable software, reusable data products and workflows that make sense to scientists, developers and decision-makers.
Occasional writing
Thoughts on scientific software, AI-enabled R&D and the systems around technical work—as and when there is something worth saying.
Why AI may change science first through the operation of research rather than through a single decisive prediction.
Scientific capability becomes more valuable when users can trust it, developers can extend it and teams can understand the assumptions behind it.
Problems that interest me:
Areas I focus on:
Focus areas
My work spans ambiguous scientific data, predictive models, AI-enabled workflows, platform choices and the move from promising demonstrations to trusted capability.
Examining architecture, model and data assumptions, workflow design and roadmap choices as parts of one scientific system.
Explore technical assessmentTurn notebooks, scripts, model demos, and scientific workflows into maintainable Python-first systems with validation, auditability, and clear user paths.
Explore scientific softwareBringing scientific, product and engineering perspectives together when a decision cannot be understood through only one of those lenses.
Read about my approachI am a scientific software and platform specialist with a computational chemistry background. My recent work focuses on Python-first platform delivery, predictive modelling workflows, scientific data products, and tools that make complex R&D capability usable.
I work across the boundary between scientific users, software developers, platform teams, and decision-makers. That is the useful overlap for early technical products: enough science to know what matters, enough engineering to know what will survive, and enough product judgement to know what people will actually use.
Alongside my full-time role, I am interested in open-source collaboration and in meeting people exploring science-led startups, including potential longer-term co-founder paths.
Strong scientific products need more than code. They need product judgement, credible assumptions, maintainable workflows, clear explanations, and a path from technical capability to everyday use.
My background also includes high-performance coaching and educational content, which sharpened how I explain complex ideas, structure improvement loops, and help people make better decisions under pressure.
System design for environments where scientific data, predictive models, developer tooling, and user adoption need to move together without losing scientific credibility.
Python-first clients, APIs, Dash interfaces, and workflow tooling built for scientific correctness, maintainability, and adoption.
Reliable access to predictive models, batch workflows, audit outputs, data verification, and migration evidence for R&D decision-making.
Explore data platforms and workflowsMaintained integration patterns and user-facing guidance that help scientists and developers use shared capabilities without duplicated effort.
I am most useful when the problem sits between science, software, product direction, and adoption. The goal is to reduce technical ambiguity and turn capability into something repeatable.
Requirements, stakeholder alignment, delivery planning, and evolution of reusable scientific data products and platforms.
Client tooling, interfaces, validation, and documentation that make model outputs useful in real decisions.
Centrally maintained APIs and clients that reduce repeated integration work across downstream platforms.
Manifest-driven execution, retries, reconciliation, and delivery-versus-audit outputs for robust scientific workflows.
Training, user guidance, office-hours-style support, and clear communication for mixed technical audiences.
The exciting part is AI. The value depends on connected data, reliable model access, clear control boundaries, and people who trust the tools. I focus on the foundations that make scientific AI credible enough to use.
Public-safe summaries of themes from complex R&D environments: platform delivery, developer enablement and evidence-led scientific workflow design.
All examples are intentionally anonymized to protect proprietary R&D information.
Worked across user needs, delivery priorities and longer-term thinking for a shared scientific data platform.
Outcome: a stronger foundation for reusable scientific data, future AI/ML readiness, and cross-team discovery workflows.
Standardized how predictive model capabilities are accessed by scientists and embedded by developers into downstream tools.
Outcome: lower integration overhead, more consistent access to model outputs, and smoother adoption across scientific and technical users.
Turned ambiguous data migration and prediction-delivery problems into repeatable, evidence-producing workflows.
Outcome: clearer migration decisions, more robust prediction delivery, and reusable operating patterns for future scientific data work.
If your work intersects with scientific software, R&D data or predictive workflows, you are welcome to get in touch. I am always interested in thoughtful technical conversations.