Reliability · keeping services up
88/100Retries with backoff, timeouts, idempotent writes and error channels that reach a human. Services that keep running after everyone has gone home.
- Linux
- Docker
- Retry and timeout design
- Structured logging
Skills
Capabilities
Seven disciplines, each with a self-assessed level and a link to the public work that exercised it.
Levels are a self-assessment, not certifications or benchmarks. Evidence links point to public repositories.
How to read this
Each entry is an engineering discipline with the developer's own estimate of depth, so compare the shape, not the digits: the profile leans toward backend work, architecture and reliability, with systems programming and security as the areas currently being levelled up.
Every card below links to a public repository where that capability was actually exercised.
Backend · APIs and services
90/100APIs and services written to be read, not just run. Typed boundaries, clear modules, documented endpoints.
- Python
- Django / DRF
- FastAPI
- Node.js
- REST
- JWT
Infrastructure · containers, proxies, manifests
85/100Linux, containers, reverse proxies and the manifests that keep them standing through long nights.
- Linux
- Docker
- Nginx
- Kubernetes
- Terraform
- Git
Systems · close to the metal
70/100C, assembly, sockets, linker scripts, and the discipline of no undefined behaviour.
- C
- Rust
- Assembly
- Make
- QEMU
Automation · scheduled work that reports back
82/100Scheduled jobs, bots and pipelines that remove the boring parts, and tell you when they fail.
- n8n
- Bash
- Python scripting
- Celery Beat
- Telegram bots
Architecture · boundaries and decisions
92/100Clean architecture, small diffs, boundaries that match the problem. Decisions written down next to the code.
- Clean architecture
- Modular design
- Typed configuration
- Documentation
Security · secrets, auth, exposure
74/100Security-minded by default: credential-free exports, secret scanning, token auth, and knowing which ports are open.
- JWT auth
- Secret hygiene
- Port scanning
- Least privilege
Written to be read
“APIs, tooling and automation, written to be read, not just run.”
Small diffs
“Clean architecture, small diffs, no undefined behaviour.”
Outlast the shift
“Build services that keep running long after everyone has gone home.”
Levelling up
“Distributed systems, security and performance.”
Adapted from the developer's own profile notes.