Deployment and delivery at Oracle Cloud Infrastructure
Across 9+ years at OCI, I built backend and platform systems for deployment,
workflow orchestration, and CI/CD, and carried changes through design,
implementation, testing, rollout, and production support.
- 90% shorter deployments; 50% fewer errors between deployment agents and the control plane. Diagnosed and corrected a capacity bottleneck in OCI’s largest region.
- Built CI/CD orchestration for a platform serving approximately 500 products and 70 active regions. Integrated formal change management with automated delivery.
- Peak region-build incident staffing reduced from three engineers to one. Led a seven-person effort addressing recurring failures.
- Rollback selection and execution across a layered deployment platform. Led three engineers delivering this capability. The broader rollback offering
recorded approximately 3,200 events over 90 days, averaging 16 minutes to
complete; a two-week window included about 110 applications and 30 teams.
I built the agent context and directed AI implementation of a virtualization
broker for local service testing, enabling functional and adversarial checks
before code review. I mentored engineers, built reusable reference
implementations, and carried operational lessons into alarms, runbooks,
documentation, and the delivery platform itself.
This work also included restructuring alerts to catch degradation before
customer impact, and overseeing a Docker support image: removing
vulnerabilities and expanding access so internal teams could more easily
meet OCI’s compliance and contract requirements. I now use Grype during
development to find known vulnerabilities and exclude them from planned releases.
- OCI
- Go
- Java
- Python
- Temporal
- CI/CD
Current projects
Codex Manager — keeping coding sessions on track
Developing a desktop application for organizing and continuing Codex sessions. It keeps the coding runtime independent of the window, preserves session history, and makes active work, pending input, and finished turns easier to follow.
Why I’m building it
An agent choosing to end its session does not mean the requested work is complete. I’m building review and continuation controls that compare the result with the actual request and send incomplete work back into the original session. The aim is to keep implementation moving toward my design rather than accepting reduced scope or a different implementation. Words in a session which imply progress do not mean the agent has progressed.
Where it stands
In active development and use. Session persistence, recovery, and review are implemented; continued work focuses on behavior across workflows in a mesh of active devices running distinct OS architectures.
Seer & UI Observation — checking software against its design
Extracting the requirements a user cares about from design text and detailed question sessions, then automatically evaluating candidate implementations against that design. Seer and UI Observation provide parts of the tooling for checking the running product’s behavior.
Why I’m building it
The useful result would be a repeatable way to tell whether software still meets the intended design, including requirements that the implementation or its own tests overlook. That would make agent output easier to assess without rereading every change or taking the agent’s summary on trust.
Where it stands
The individual tools have working implementations. The complete process is still in development and is not ready for other people to use. Making it both effective and efficient remains a central focus.
Writ — useful agent access with explicit authority
Developing a system for letting agents inspect an authorized view of a machine, prepare work, and request approval for changes through the host’s normal tools and shells.
Why I’m building it
I want to use my agents to help fix problems on my parents’ personal computers without giving the agents default write or administrator access. Writ exists to make those changes depend on my judgment about what should happen, rather than the agent’s judgment.
Where it stands
Development implementation. Native inspection and execution paths exist; complete human-approval and remote workflows are still being developed and tested.
Cambiform — source-aware versioning
An experimental versioning tool for working with changes in source-code structure. A separate benchmark harness compares its public operations with Git on real repository histories and checks the restored results.
Why I’m building it
Concurrent changes can overlap in a file without affecting the same things. I’m exploring whether a tool that understands source structure can make those changes easier to combine while preserving the exact code that should survive.
Where it stands
Experimental implementation with restore, history, and merge work. Comparisons are scoped to the repositories and checks actually run.
OpenReplication — encrypted backup between machines
A command-line backup preview that encrypts files on the owner’s machine and stores versions on an OpenCloud share offered by another machine. It includes status, verification, and recovery workflows.
Why I’m building it
I want backup arrangements where someone can provide storage without receiving the contents of the files. Recovery is the deciding behavior: a successful upload is useful only if the owner can get the right files back.
Where it stands
CLI preview. Backup and recovery can be exercised now; the broader replication and first-use experience remain under development.
DirStat and backup migration. A Rust disk-usage analyzer for inspecting directories, backups, archives,
and WSL disk images, alongside an importer for preserving older Windows
backups in a modern backup repository. These address practical questions:
what is taking up space, what is in an old backup, and can I recover it
without first expanding the entire collection? DirStat source · Backup importer source
Four Words. A native desktop app and CLI for generating passphrases from bundled
dictionaries, with controls for the length and character requirements
imposed by the service where the phrase will be used. Download the latest release
Tax Calculator. A local Rust desktop tool for comparing income and payment scenarios.
It keeps recorded amounts separate from assumptions about future income
so the basis of a projection stays visible.
To discuss this work or a problem you need solved, get in touch.