KEEL

24 notes filed under KEEL, newest first. Same rules as the rest of the pile: a codename, a theme, and no internals.

codename KEEL · 24 notes · 24 themes · all codenames

all themes alert-delivery 1 backup-and-restore 1 bootstrap-ordering 1 certificate-issuance 1 certificate-lifecycle 1 declarative-imperative-gap 1 drift-detection 1 exposure-defaults 1 identity-services 1 incident-tooling 1 leadership-naming 1 lockout-safe-provisioning 1 machine-identity 1 mail-and-webmail 1 migration 1 one-writer 1 posture 1 redundancy-judgement 1 reproducibility 1 scheduled-jobs 1 secret-delivery 1 service-discovery 1 storage-layout 1 verification-design 1

KEEL · scheduled-jobs · 2 min read

a scheduled job runs somewhere, whether you said where or not

A periodic job is two contracts, and only one of them gets written down. The first is what it does. The second is where it is allowed to do it, and that one stays implicit in the job's body: it reads a directory on a local disk, or a socket…

read

elsewhere

Other codenames

Each codename is a project. The theme is the class of problem the note is about — the same theme recurs across projects, which is usually the interesting part.

ABACUS 60 FLINT 12 KEEL 24 LARDER 24 LATTICE 36 MERIDIAN 24 MISE 24 SCRIBE 12 TROUPE 12 UMBRA 24 browse 244 themes

KEEL

KEEL notes

a scheduled job runs somewhere, whether you said where or not

Other codenames