About
Software engineer, backend-minded
I am a software engineer interested in the parts of an application users do not see: the APIs, data models and services that make it dependable. I started with HTML, CSS and JavaScript. My work now spans React and TypeScript front ends, PHP and Node.js back ends, and Go services.
Recent projects include a Go monitoring server with a time-series store, alert rules and a query API, and IRAS, a TypeScript web application for automating inspection reports, built on Firebase. I have also built client web projects with React, Tailwind CSS and Firebase, along with many smaller front-end exercises that are in the archive.
I am building my Go and backend skills through a 24-week industrial training programme (SIWES), covering REST APIs, gRPC, PostgreSQL, Docker, Kubernetes and JWT authentication.
Start from the data and the contract
Before building screens, I decide what the data looks like and how the API will expose it.
Keep dependencies small
The monitoring server is built with no third-party dependencies. I prefer explicit code when the problem allows it.
Test the parts that fail
Parsers, state transitions and configuration validation are where I put tests first.
Document the limits
Every project should say what it does not do. The monitoring README lists its limits openly, and I think that is the right default.