Arthur Costa

Operations read so far: A 0/0 on replica A, at work;B 0/0 on replica B, own time;partitioned

Apart, then equal. · two replicas of one profile, merged without a coordinator

Arthur Costa

Senior backend & platform engineer · Porto, Portugal

fields both replicas agree on span the partition

Replica A · at work

I build platforms that hold up in production: moving fleets to the cloud, turning batch into event streams,

Replica B · on my own time

and, on my own time, execution platforms and safety tooling for coding agents.

    partitioned

      Open to senior backend or platform roles, remote or hybrid

      The portrait is partitioned too: replica A is the main view, replica B the inset, each taking its own edits. When the partition heals, B slides into A, edits made on both resolve by timestamp and both hold my face; the partition through my name closes at the same moment.

      Partitioned: two replicas, edited apart one line per operation

      Every role and decision record is an operation on one of two replicas. Read either side in any order: the columns do not line up, because replicas have no global order, only their own. Each record shows its outcome; open it for the case study.

      Replica A · at work

      0 ops

      Replica B · on my own time

      0 ops

      The heal · both op logs, on one time axis, merged without a coordinator

      Merged: every record, joined on id rows arrive from the replica that wrote them

      idrecordwritten onoutcome

      Tombstones, pruned only when every replica has them AC-009

      In my offline-first sync tool, a delete leaves a tombstone, and the tombstone is pruned only once every active desktop has applied it. Three desktops, one delete; one desktop is offline when it happens.

        What both replicas agree on no conflict to resolve

        Rules · habits

          Fields

          Stack · the union of both replicas’ tools

          Reach me Open to senior backend or platform roles, remote or hybrid

          converged: both replicas hold the same photo

          Reach me on LinkedIn or GitHub. Whichever replica you write to, the message arrives.

          Why this design colophon

          Concept. I built offline-first sync that converges without a central source of truth, so my profile is two replicas, at work (teal) and on my own time (ochre), edited apart and merged without a coordinator.

          Information architecture. The first screen is the partition: what both replicas agree on spans the dashed line, each half of my one-liner and its results sits on its side, and the portrait heals across it. Below come the two op logs, each record showing its outcome and opening in place; the heal, drawn as both logs converging on one axis; the merged state as a join on id; the tombstone rule from AC-009; and one section for everything both replicas already agree on.

          Portrait. The header portrait is your version vector: cells written on A fill in as you read A, cells written on B as you read B, and the heal fills in what you skipped. The page ends on the converged photo.

          Typography. Sono carries headings, labels and counters because its MONO axis is the merge: a dashed partition runs through my name, Arthur in teal and Costa in ochre; when the replicas converge it closes, the letters turn ink and fully monospaced, and headings are proportional above the heal and half-monospaced below it. Every sentence is set in Literata, a reading face drawn for the same book on many devices.

          Colour and motion. Teal and ochre are a complement and a neighbour of my skin tone, always paired with a label. The two new animations, the logs converging and the tombstones, are merge rules I have used; the portrait plays once and holds.

          Accessibility. “Pause animation” stops everything and reads “Resume animation” while paused; reduced motion shows every end state; each figure has a written equivalent; every control is at least 44 px.

          Complete profile

          Senior backend & platform engineer · Porto, Portugal

          I build platforms that hold up in production: moving fleets to the cloud, turning batch into event streams, and, on my own time, execution platforms and safety tooling for coding agents.

          Open to senior backend or platform roles, remote or hybrid

          Nine years in production (since 2017)

          Decision records

          2023–2025 · At work · Platform · Delivered

          200+ instances to cloud local zones, with autoscaling

          Compute cost fell by ~70% across 200+ instances.

          ~70% lower compute cost — 200+ instances moved from on-prem and edge sites to cloud local zones, with autoscaling

          200+ instances migrated — with autoscaling, for live sporting-event peaks

          Context and decision

          Context. A real-time platform for live sporting events ran its workloads on on-prem and edge environments.

          Decision. Lead the infrastructure modernization: migrate the workloads to cloud local zones and enable autoscaling, with multi-region load tests before peak events.

          Stack. Cloud local zones · Autoscaling · Go · Python · Locust

          2022–2023 · At work · Payments · Delivered

          Payment settlement, from batch to event-driven

          Processing success rose from 60% to 90%+.

          60% → 90%+ processing success — payment settlement moved from batch to event streams with change data capture

          Context and decision

          Context. A legacy payment and settlement platform ran as batch processing on a monolith.

          Decision. Move the core components to Java and Go, replace batch with streaming and change data capture, containerize on Kubernetes, and centralize logs and dashboards for the SLAs.

          Stack. Java · Go · Streaming · CDC · Kubernetes

          2026 · Own time · Platform · Working system

          Horus: remote execution for builds and agent jobs

          A changed worktree is a new job, never a silent retry; a worktree without a data class never leaves the machine.

          Context and decision

          Context. Builds and coding-agent jobs start on a workstation but need the CPU, isolation and uptime of a remote fleet, without leaking a private worktree or losing work halfway.

          Decision. A local daemon with a socket API and a written durability contract; content-hash sync so a job runs on exactly the bytes submitted; recovery bound to that content; a versioned accounting ledger; gVisor sandboxes on VPS runners behind a data-class gate.

          Stack. Go · Rust · gVisor

          2026 · Own time · Virtualization · Spike

          Firecracker microVMs as a sandbox compute driver

          A failure-injection suite on a KVM host (kill mid-create, simulated reboot, duplicate RPCs, kill points 0–50 ms, a leak counter) and 23 security probes on a 22-item adversarial matrix. An unimplemented check reports SKIP, never PASS. Proposed upstream as OpenShell#4351.

          Context and decision

          Context. Can Firecracker microVMs, with the jailer, back an open-source agent sandbox runtime (OpenShell) through the whole lifecycle, and stay correct when things crash?

          Decision. A compute driver with its own guest kernel, images from a verified catalog, reclamation of the previous run's VMs at start-up, and a guest flush before Stop.

          Stack. Go · Firecracker · KVM

          2026 · Own time · Platform design · Accepted

          Retire my own agent platform; keep the native clients

          Far less to operate; contribution rules now refuse new routers, schedulers and dashboards.

          Context and decision

          Context. My agent-workflow repository had grown a router, a scheduler, a coordinator hierarchy, a provider dispatcher and a dashboard in front of three coding-agent clients.

          Decision. Retire it (19 October 2026). Each client runs natively; the repository keeps shared skills, a small configuration, standalone safety tools and 26 dated decision records.

          Stack. Python · Bash

          2026 · Own time · Platform safety · Accepted

          Safety tools fail closed

          Documented as a tripwire, not a sandbox, so nobody mistakes it for isolation.

          Context and decision

          Context. Coding agents run shell commands in real repositories from three clients with three hook systems; secrets once reached a model through process arguments.

          Decision. One command-safety hook for all three clients; output redaction; long-lived credentials kept out of worker reach; a missing safety dependency refuses instead of being caught and allowed.

          Stack. Python

          2026 · Own time · Distributed systems · Lab

          Course labs on microVMs, behind an mTLS control plane

          A lab's user id stays reserved until its cleanup has succeeded; CA rotation cannot be bypassed by session resumption.

          Context and decision

          Context. A course platform gives every learner a disposable lab machine, created and destroyed constantly by many people at once.

          Decision. A microVM lab runtime with a chaos test that kills VMs mid-session; idempotent resets by key; mutual TLS on a control-plane CA with reload without restart; pinned keyless signing that fails closed.

          Stack. Go · Kotlin · protobuf

          2026 · Own time · Storage & consensus · Study

          A relational database, from storage to Raft

          Built layer by layer as a study; each phase is a commit history.

          Context and decision

          Context. The fastest way to understand a distributed database is to build its layers in order and see where each guarantee comes from.

          Decision. Disk manager, buffer pool, B+ tree, heap file and write-ahead log; SQL parser, planner and Volcano executor; 2PL then MVCC; Raft, Multi-Raft with range sharding, Percolator-style transactions, SSI with hybrid logical clocks, an S3 backend and the PostgreSQL wire protocol.

          Stack. Rust

          2026 · Own time · Sync & security · Working system

          Offline-first sync with signed form-fill

          The extension never fills a form the owner did not approve.

          Context and decision

          Context. A personal job-search tool runs on several desktops plus a browser extension; data must sync without a central source of truth.

          Decision. Tombstones pruned only once every active desktop has applied them; fill tokens signed on the desktop with a P-256 key from the OS keyring; an encrypted vault export; an LLM judge measured against blind readings.

          Stack. Go · Rust

          2025–2026 · Own time · Developer tooling · Shipped v2.1.1

          gitshift: many Git identities, one machine

          Switching on a directory change went from about 3.8 s to about 0.5 s.

          3.8 s → 0.5 s directory switch — gitshift identity switch on directory change, release v2.1.x

          Context and decision

          Context. Several GitHub and GitLab accounts on one machine means juggling keys, identities and signing by hand.

          Decision. One command switches Git author, SSH key, commit signing and the GitHub CLI account, by alias or automatically by directory; releases through GoReleaser and a Homebrew tap.

          Stack. Go · GoReleaser · Homebrew

          Project source

          Experience

          1. Software engineer, core call control

            2025–2026 · Cloud contact-centre platform

            Load tests to inform cost optimization and Kubernetes autoscaling; graceful shutdown and connection draining in a shared Helm chart; CI repaired with quality gates; codebase rules for agentic coding, shared with the team.

          2. Software engineer, platform / backend

            2023–2025 · Real-time platform for live sporting events

            Led the move of on-prem and edge workloads to cloud local zones with autoscaling (AC-001); real-time, event-driven services on serverless and containers; Go and Python automation; Locust multi-region load tests for peak events; CI/CD across GoCD, GitHub Actions, Jenkins, Buildkite, Ansible and Packer; metrics, logs, traces and alerts.

          3. Software engineer, payments / settlement

            2022–2023 · Payment and settlement platform (consulting)

            Led the modernization of a legacy payment and settlement platform to event-driven streaming and CDC (AC-002).

          4. Software engineer, post-purchase

            2021–2022 · E-commerce marketplace, several countries

            Backend services in Go, Java, Node.js and Groovy for post-purchase and payment workflows; faster claim and dispute resolution.

          5. Software engineer

            2019–2021 · Core banking, Brazil

            Monoliths and mainframe-based systems modernized into Java and Spring microservices; migration of microservices to the public cloud under regulatory SLAs.

          6. Associate software engineer, CRM & integrations

            2018–2019 · Fintech CRM

            Real-time CRM features integrated with banking services such as loans, OTP and account management.

          7. Associate software engineer

            2017–2018 · Software house

            CRM and warehouse management systems in PHP and JavaScript.

          How I work

          Also built

          Drover

          Watch and approve agent sessions from any device: a Rust core over UniFFI, pairing scopes bound to the consumed token.

          Rust

          JVM performance labs

          Eleven on-heap versus off-heap lock-free scenarios with JMH, and 13 serialization frameworks behind one endpoint. Numbers not quoted until re-run with raw output.

          Java · JMH

          graphql-federation

          Federation 2 across Java, Go and TypeScript subgraphs, gRPC between services, SLO burn-rate dashboards.

          Java · Go · TypeScript · gRPC

          Ponte

          A management system for tutoring schools: live lessons with recording and consent, TOTP and lockout, a finance ledger ported to Go and checked by replaying a shared corpus.

          TypeScript · Go · PostgreSQL

          deep-engineering-knowledge-base

          An LLM pipeline that writes and checks engineering lessons, with an independent critic that excludes the author.

          Python

          techish-visual

          An engine for animated technical diagrams: a ThorVG WASM renderer and performance budgets in CI.

          TypeScript

          keyframe

          A Linux studio for recording and editing technical videos, with cuts snapped to silence.

          Rust

          java-workflows

          Reusable GitHub Actions for Java teams: a Java 11 to 25 matrix, security scanning and SBOMs.

          GitHub Actions

          Upstream

          OpenShell#4351

          Firecracker compute driver proposal, from AC-004 (open source). · open

          OpenShell#4591

          A gateway reporting "database is locked" under two concurrent clients. · open

          Orca, 10 pull requests

          SSH OAuth forwarding, pairing-offer rotation without restart, security events, isolation from external agent config. · 9 open, 1 closed

          Stack

          Languages
          Go · Java · Python · TypeScript · Node.js · Rust · Kotlin
          Cloud & runtime
          Kubernetes · GKE · GCP · AWS · Helm · Serverless · Firecracker · KVM · gVisor
          Data & messaging
          Kafka · RabbitMQ · Streaming & CDC · PostgreSQL · MongoDB Atlas · Raft · MVCC
          Delivery
          GitHub Actions · GitLab CI · GoCD · Jenkins · Buildkite · Ansible · Packer · Terraform · Locust
          Observability
          OpenTelemetry · Grafana · Loki · Tempo · Mimir · Datadog · Dynatrace · ELK
          Earlier
          Spring · gRPC · Istio · Akka / Pekko · GraalVM · PHP

          Community

          Tech.ish Thoughts, a collaborative tech blog and GitHub organization (actors, JVM serialization and off-heap work, reusable CI, gitshift).

          The Actor Model, at a DevOps community meetup in Porto.

          Mentors Brazilians entering software engineering through an NGO.

          Background

          Associate's degree, Systems Analysis and Development (2016–2018).

          Portuguese (native), English (full professional, C2), Spanish (limited working).