Cloud estate management
2020–2024
Smarter.Codes' internal effort to audit its cloud servers and cut hosting cost.
Cloud and Platform
Infrastructure Provisioning
I provisioned and managed cloud infrastructure through code for internal engineering estates and client deployments.
See its threads in the worldUsed on
Internal engineering estate
2022–2024
Smarter.Codes' internal estate: a MediaWiki and Wikibase documentation portal, public website and engineering consoles used by staff.
Internal starter codebases and CI/CD
2021–2025
Internal starter codebases and CI/CD tooling so new company projects skip setting up delivery from scratch.
Company website estate
2023–2024
Smarter.Codes' in-house software estate behind its public site: crawler, automation framework, natural-language stack and chatbots.
Regulatory medical-writing platform
2023–2026
A platform that drafts regulatory documents for clinical trials from source evidence, built for a pharmaceutical documentation firm and its sponsors.
Internal proposal management
2020–2023
Internal software that watches freelance marketplaces and social networks for worthwhile opportunities, plus a writer that drafts grounded cover letters.
Address-directory crawling estate
2020–2021
Crawling and address-extraction system that builds a directory of the physical locations of internet businesses from public web pages.
NLX entity-extraction API
2022–2023
Natural-language API that returns entities, facts and a parse tree from domain-specific text such as ingredient declarations and medical supply descriptions.
SEO analysis platform
2016–2021
SEO analysis product that crawls a customer site, analyses its pages and turns findings into assignable tasks for marketing teams.
Objective.Earth public catalogue
2022–2025
A public, editable wiki cataloguing environmental and social problems, their proposed solutions and the projects addressing them.
Stories where it mattered
2026 · Regulatory medical-writing platform
A cache that remembered the failures
- Situation
- On a regulatory document platform, generated documents came out wrong in ways that did not reproduce, and retries repeated the bad output.
- Task
- Find the true cause in a pipeline whose output reaches a client in a regulated industry.
- Action
- I traced it to a global result cache that also stored partial failed runs, then re-architected generation around per-step isolation with failure-aware cleanup.
- Result
- Failed runs stopped affecting later ones, a retry became a real retry, and the written root cause let the team review it.
2026 · Regulatory medical-writing platform
Tables that arrived in the client's document as raw markup
- Situation
- Medical writing deliverables showed misplaced tables, detached titles, and sometimes raw markup visible as text in the client's document.
- Task
- Produce one root cause analysis for three separately reported bugs before anyone wrote a fix.
- Action
- I found three causes: raw XML mutation, incomplete model-emitted HTML, and context-blind placeholders. I moved tables to a structured contract with neighbour context.
- Result
- The whole class of defect went away, not just the three reported instances.
2024 · Regulatory medical-writing platform
Asking what onboarding was supposed to produce
- Situation
- Two engineers were joining a document platform module covering audit logs, automatic mapping and server management.
- Task
- Give onboarding an intended outcome rather than just an activity.
- Action
- I asked the lead for the target outcome, how we would judge pace, and when production value was expected, and offered a reference checklist.
- Result
- Onboarding ran against a stated target and a first-value date, and the checklist was reused.
Goes with
Terraform
Kubernetes
Docker
CI/CD
SRE
ObservabilityThrow me a paper plane
Write a line; I’ll find it in my inbox.