Why a rocket, why a cacique
A cacique was a Taíno chief — the person responsible for the village actually working. That’s a fair description of infrastructure work, minus the feathers. The rocket part is aspirational: I like building the platforms other things launch from.
I’ve been doing that for 28 years at one organization, which is unusual enough to be worth writing about on its own. I started in 1998 fixing staff computers; today I run a Terraform-managed AWS platform and the AI tooling on top of it. Every era of that stack — Citrix farms, Oracle middleware, datacenters, containers, LLM guardrails — taught something the next era needed.
This blog is where those lessons go. Four kinds of posts, every other week or so:
- Technical — patterns from infrastructure-as-code, AWS operations, and AI tooling.
- Projects — side builds, like teaching an ESP32 to read a 1990s alarm panel.
- Career — what 28 years in one org teaches you that job-hopping can’t.
- Faith — I work in ministry tech; sometimes that perspective is the point.
One rule governs everything here: I write about lessons, never about specifics that belong to my employer. No internal systems, no incident details, no clever architecture diagrams of things I don’t own. If a post ever reads vague in a spot, that vagueness is load-bearing.
If any of this is useful to you, the RSS feed is the way to follow along.