About

I work as a software orchestrator and full-stack developer — directing AI coding agents, making architecture decisions, and delivering production-quality software across the full stack. I do not treat this as mechanical coding; I treat it as a craft. Building something functional from nothing, watching it handle real load, and improving it based on what production data shows — that is what I find genuinely interesting. I keep learning new tools and domains because the craft itself is the motivation, not the specific technology.

The range of work is wide: Python and FastAPI service backends, Node.js and TypeScript applications, real-time operator dashboards, web applications, standalone desktop-style tools, WordPress themes and plugins, on-chain swap execution and blockchain monitoring, trading automation, video processing with GPU-accelerated transcription, crypto payment architecture, data engineering pipelines, hardware telemetry dashboards, service management infrastructure, and more. The consistent standard: software that runs in production, not a demo that worked once.

A significant part of what I build is data-intensive: exchange WebSocket feeds, on-chain events, gas price streams, holder distribution snapshots, aggregated trading analytics, resource and hardware metrics. I build the ingestion, normalisation, aggregation, caching, and the front end that makes the data actionable. The recurring engineering challenge is making this work reliably on real hardware rather than provisioning more infrastructure around the problem.

I also build tooling to improve my own operations. When existing solutions were not good enough — monitoring that did not show what I needed, service management that required SSH for every change, hardware data with no useful interface — I built replacements: a custom service manager that controls every process, Docker stack, systemd unit, and firewall rule from one browser dashboard; a hardware monitor with live telemetry; a Linux system TUI with CPU, memory, disk, network, GPU, and sensor data. I deploy on VPS, dedicated servers, Docker containers, and cloud infrastructure depending on what the project needs.

Code lives in private repositories. Public overview repositories on GitHub cover what each project does, the architecture decisions behind it, and who it is built for. The blog documents real engineering problems — decisions made, things that broke, and what actually fixed them.