Internal engineering estate
2022–2024
Smarter.Codes' internal estate: a MediaWiki and Wikibase documentation portal, public website and engineering consoles used by staff.
Cloud and Platform
Nginx
I deployed Nginx reverse proxies across the company's internal infrastructure as a gateway routing traffic.
See its threads in the worldUsed on
Company website estate
2023–2024
Smarter.Codes' in-house software estate behind its public site: crawler, automation framework, natural-language stack and chatbots.
Cloud estate management
2020–2024
Smarter.Codes' internal effort to audit its cloud servers and cut hosting cost.
Internal operations desk
2022–2024
An internal operations desk handling equipment, tool accounts, time tracking, invoices and interview logistics for Smarter.Codes staff.
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.
Kray.AI search and document assistant
2021–2024
An AI search and document-assistant platform sold as Kray.AI, with a WooCommerce plugin and a demo store.
Paid trading community platform
2020–2024
A paid community for stock traders: a membership site plus a chat server with in-conversation price charts.
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.
Medical-device monitoring for hospitals
2019–2021
Monitoring and remote-access system for hospital medical devices: live dashboards and alerts for staff, browser-based remote access for service engineers.
Stories where it mattered
2024 · Kray.AI search and document assistant
One model for everyone, or one per customer
- Situation
- A document assistant for a fleet operator needed an architecture, and one model trained on every vessel's documents was the assumed default.
- Task
- Lay out the real trade-offs of cost, latency and access control instead of just picking one.
- Action
- I wrote both options out for client and team: one shared model versus one model per vessel, with pros, cons and the replica arithmetic.
- Result
- The partitioned design went forward, with the loss of cross-fleet questions accepted openly.
Goes with
Docker
Terraform
Kubernetes
Express
CI/CDThrow me a paper plane
Write a line; I’ll find it in my inbox.