Frank Cancedda
02 · about

The long version.

Home is the resume. About is the worldview — how I work, and the principles I'd defend in a design review.

Bio · TL;DR

I'm a tech lead and platform engineer based in New York. My day job is owning the infrastructure that ML teams ship on — Kubernetes, inference servers, CI/CD, and the developer-experience tooling that collapses a 40-minute “set up your laptop” into a single command. I led a 3-person platform team at Technergetics through 2024 — sprint planning, hiring input, and the architecture calls — and now carry the domain as tech lead.

Before that, I trained as an applied mathematician and data scientist. That side of the brain still drives most of what I find interesting: tiny models that beat big ones, retrieval policies that learn, the unreasonable effectiveness of well-placed caching.

I also run a self-hosted Kubernetes homelab with full GitOps, SSO, observability, and CI/CD, and I'm building Vivazo — a Rust game engine targeting WASM. Both are how I keep the systems parts of my brain sharp on weekends.

Tech leadPlatform engineeringML systemsSelf-hoster
Right now03 · currently
Building
Tilt + k3d dev platform for an AI inference stack of 40+ services and jobs
Researching
Cost-aware retrieval policies (REINFORCE, BEIR)
Running
Self-hosted k8s homelab — Flux GitOps, Authelia SSO, Traefik, Grafana
Making
Vivazo — a Rust game engine targeting WASM
Reading
"Less is More: Recursive Reasoning with Tiny Networks"
How I work04 · principles
01

Keep production boring

Production should be unsurprising. Save the cleverness for the parts that move the needle — the inference path, the retrieval policy, the model contract. Everything else is plumbing, and plumbing should be conventional.

02

Make it one command

Anything an engineer types more than three times deserves a script. Anything a team types more than three times deserves a platform.

03

Mirror prod in dev — actually

Half-faithful local stacks are worse than no local stack. If staging passes and prod fails, your dev environment lied. The hard part is bringing up the real dependencies together, because bugs live at the seams between services.

04

Measure the path, not the model

Most ML wins come from the retrieval policy, the eval harness, the cache hit rate — not the LLM. A small model in the right place beats a big one in the wrong place.

Education05 · education
2020 — 2022

M.S. Data Science

University at Albany, SUNY

Focus on statistical learning, NLP, and large-scale ML systems.

2015 — 2019

B.S. Computer Science & Applied Mathematics

University at Albany, SUNY

Dual major. Research support specialist (2019—2020) before grad school.