Cloud and Platform

Docker Compose

I set up Docker Compose configurations for local development and automated testing across multiple projects.

Used on

2021–2025

Internal starter codebases and CI/CD tooling so new company projects skip setting up delivery from scratch.

2023–2026

Hosted self-serve platform where businesses build chatbots from visual blocks and deploy them on web, WhatsApp and Mattermost with human handover.

2023–2024

Smarter.Codes' in-house software estate behind its public site: crawler, automation framework, natural-language stack and chatbots.

2022–2024

Smarter.Codes' internal estate: a MediaWiki and Wikibase documentation portal, public website and engineering consoles used by staff.

2023–2024

A hotel product where guests record food preferences by QR code so kitchens can predict breakfast demand and cut waste.

2021 · Hybrid.Chat conversational platform

Situation: The chatbot platform's runtime holds conversation state in memory, so under high availability any pod restart dropped live conversations.
Task: Survive pod churn without rewriting the conversational runtime the product was built on.
Action: I checked alternative frameworks, found the same limit, and kept the runtime: sticky sessions, state persisted to Mongo, and Redis pub/sub to close duplicates.
Result: The platform ran multi-container with state surviving restarts, and the design documented its failure modes, including those the fix introduced.

2023 · Hybrid.Chat conversational platform

Situation: The bot platform needed web push notifications, and my instinct was to build it in house for future flexibility.
Task: Decide between building and buying, separating engineering reasons from personal preference.
Action: I wrote down what I wanted from in-house, weighed it against what the release needed, and recorded the preference and the decision against it.
Result: We shipped on the vendor, and the recorded trade-off made later customisation questions easy to answer.