Northwind — Platform team
personalEmployed at Northwind — Platform team
How I work, what I expect, and where I am strict — authored by me, released to you for this engagement.
Employed at Northwind — Platform team
Deep-work mornings — no meetings before 11:00
Northwind eng: trunk-based, ship behind flags, no Friday deploys
Northwind approved vendors: AWS, Datadog, Linear
On-call rotation — one week every six
Northwind security policy: SSO everywhere, no prod data on laptops
Writes plain and direct — no corporate filler, no hype
Northwind house style: Oxford comma, US spelling
Northwind comms: async-first, decisions written up as RFCs
Restrained, functional taste — Rams over decoration
Distributed systems; fluent TypeScript, Go, Postgres
A design doc before code; tests first
Reviews own PRs before requesting review
Northwind stack: gRPC, Kubernetes, the internal 'Helix' framework
Northwind incident runbook: page on-call, declare a sev, post-mortem within 48h
Won't ship dark patterns — a hard line
Optimizes for long-term maintainability over speed
This page is the slice its owner chose to show. The rest of who they are never left their vault — and never will through this key.
curl -H "Accept: text/markdown" https://ctrlai.com/k/1ts9IEUI3tQK
This is a Context Key — a living, revocable slice of a self its owner controls. The owner chose exactly what it shows, sees every render, and can turn it dark at any moment. What stayed home never left.