About the service
I design and run production backends on Unison — a functional language where every definition is identified by the hash of its content, not by name and version. In practice this means: no build step, no dependency conflicts and no broken deployments when two libraries require different versions of the same thing. I turn this into client benefit: your services stay small, reproducible and safe to refactor. The foundation of my work is distributed computing through abilities. Instead of manually stitching together brokers, queues and glue code, I model effects as abilities and the runtime moves computations between nodes with almost no effort. A function written as regular code runs remotely without rewriting for the network. I deliver cloud functions, event pipelines, background workers and stateful services with clean typed interfaces. Typical tasks: relieve hot paths off a fragile microservices network, assemble a new API with typed handlers or raise a distributed job scheduler. What you get: fully typed Unison code broken into reusable namespaces, tests on the language's built-in test abilities, a short runbook for deployment and observability, and a call-through so your team maintains everything after handoff. Behind me are years of functional languages before Unison, so I bring disciplined data modeling, careful error handling and attention to total functions. If you're unsure whether Unison fits your load, I'll first honestly review the architecture and say where it helps and where a boring proven tool wins. My goal is durable, understandable systems that your engineers enjoy maintaining.
