— 0113.06.2025
what i know about docker
Images, layers, and the bits of the daemon that actually matter when a container will not start.
read↗hi.
i’m dextey
developer / systems tinkerer
a.k.a
[ full stack engineer & cloud architect ]
interfaces on top,
infrastructure below. i work across web systems, networking and
security deploys, packets, containers. building things that stay fast
under load and boring under pressure.
DESIGN // CODE
HOST: LINUX/NGINX
UI_VER: 2.1.0
UI_VER: 2.1.0
02 / LEDGER05 GROUPS · 14 ITEMS
what i build,
how i think.
A spec sheet, not a skill bar. Each line is a thing I have shipped and would ship again, grouped by the layer of the stack it lives on.
136 h
a 28
b 16
c 40 NAME 132/800 mono ROLE 34 serif italic
1240 w · 24 gutter
b 16
c 40 NAME 132/800 mono ROLE 34 serif italic
01
02
03
04
05
06
07
[ 01 · interface ]
Frontend engineering
react · ts · vite
Component systems that survive a redesign. State kept
boring, boundaries kept obvious. Six production apps.
Motion & interaction
css · gsap · web anim
Transitions with a physical logic: mass, damping, and a
single easing family across the whole product.
Web performance
LCP < 1.2s
Budget first, features second. Critical path, image
pipeline, font strategy, measured on real hardware.
[ 02 · service ]
API development
node · go · grpc
Surfaces that age well: versioned, typed end to end, and
documented in the same commit as the change.
Database systems
mongodb · redis
Documents modelled around read patterns. Indexes chosen from
real query plans, migrations that are reversible.
Auth & security
oauth2 · oidc · jwt
Least privilege by default, secrets out of code, threat
model written down before the ticket closes.
[ 03 · systems ]
Linux
shell · systemd · fs
Comfortable in a bare box with no dashboard: the filesystem,
the process table and the logs.
Networking
tcp/ip · dns · tls
Protocol topology and packet flow. Debugging with
tcpdump rather than guesswork.
Hardware architecture
asm · circuitry
A computer engineer’s mental model: the physical layer
under every abstraction above it.
[ 04 · cloud ]
Cloud computing
aws · cloudflare
Infrastructure described in code so nothing lives only in
one person’s memory.
Containers
docker · k8s
Reproducible images, honest health checks, resource limits
set on purpose.
Distributed systems
queues · microservices
Idempotency, backpressure, retries with jitter. Assume every
hop fails eventually.
[ 05 · delivery ]
CI/CD
actions · deploys
Small commits, fast pipelines, and a rollback that takes one
command and no meeting.
Observability
logs · traces · slo
If it is not measured it is not shipped. Alerts that page a
human only when a human helps.
03 / WORKCURRENT ROLE
technical developer
at trakgene.
Genomic record platform serving NHS clinics. I own the React front-end, the task pipelines behind pedigree rendering, and the auth layer, from the RBAC model through to the audit trail.
STACKReact · Node · MongoDB
AWS · Docker
AWS · Docker
04 / SYSTEMSRUNTIME
it is systems,
all the way down.
Under the interface: processes, packets, queues, and the logs that prove any of it happened. This is the half of the job nobody screenshots.
99.95%uptime target
<1.2slcp budget
p95 182mstraced
$
05 / WORDSBLOG.DEXTEY.IN · 02 LIVE · 01 DRAFT
— 0223.03.2025
why i started writing blogs
Notes to my future self, kept in public. On writing as a debugging tool, and why a rough devlog wins.
read↗
— 03DRAFT
tracing a request
end to end
$ git commit -m "wip"
status: unpublished
end of filesay hi
hi@dextey.in
Open to full-stack and infrastructure work, and to a slower conversation about systems, type, or anything drawn on a grid.