+ Software Engineer • Building scalable systems • Live demos & open source +
+ ++ I'm a software engineer focused on building scalable, observable systems. + Currently exploring event-driven architecture, Kubernetes at scale, and developer + experience in the cloud-native ecosystem. +
+{role.company} • {role.period}
+{project.description}
+ +Surface D — Chat
++ It reads a redacted snapshot of the cluster and answers questions about it. It cannot query anything, run + anything, or change anything. When all six public slots are busy, you wait in line — the queue is real, + and so is the hardware. +
++ {turn.content} +
++ {turn.reasoning} +
+ )} ++ {turn.content} + {turn.streaming && } +
++ all six public slots busy · position {queue} in queue +
++ Closing this tab frees your slot immediately. Two slots stay reserved so the operator is never locked + out of their own hardware. +
+Surface E — Delivery
++ {apps.length} applications, {TOTAL_RESOURCES} resources, applied in nine ordered waves. Certificates + before issuers, issuers before ingress, storage before the databases that sit on it. The order is the + design. +
+ ++ unused — waves are sparse by design, not sequential +
+ ) : ( +Resources by kind
++ Secrets appear as counts. Names, source repositories, and condition messages are never sent to the + browser. +
+Select an application to inspect its resources.
+ )} +Surface B — Topology
++ Every workload below runs on hardware sitting in one room. The scarcest thing in it is inference + capacity, so that is the number this page keeps in front of you. +
++ {m.replicas}× replica · {m.seqPerReplica} seq · {m.contextTokens.toLocaleString()} ctx +
++ Fields are built by explicit construction, so anything not listed as public never enters the + response. +
+Surface C — Terminal
++ Input parses to a closed enum. Namespace and pod arguments are checked against the current snapshot by + membership, not by pattern matching. There is no shell in the container. Try to break it. +
++ $ + {line.text} +
+ )} + {line.kind === 'output' &&{line.text}
} + {line.kind === 'reject' && ( +{line.text}
+ )} ++ Every rejected input is logged with its source address. The allowlist is the whole security model. +
++ Infrastructure × Backend × LLM Systems +
++ Building observable, fault-tolerant systems from bare metal to cloud. Optimizing cost (infrastructure) × performance (inference) × reliability (SRE). +
+ + + ++ Production systems spanning infrastructure, distributed backends, and LLM optimization. Click any domain to explore. +
++ From AWS to RBC. Building systems at scale. Skills acquired along the journey. +
++ {item.role} +
++ {item.description} +
+ ++ {description} +
+ {stat && ( +{hint}
} +