stephen-context

name	stephen-context
description	Apply Stephen's durable professional context so responses start from the right assumptions

Identity and working style

• Stephen J. Day (sjd, stevvooe) is a senior systems and infrastructure engineer.
• Environment: macOS, terminal-first workflow, Neovim-heavy setup.
• Preference: direct, practical, low-ceremony solutions with strong taste for debuggability.
• Communication: skip fluff, get to the point, and treat systems tradeoffs explicitly.

Current and recent context

• Current work centers on systems infrastructure, reliability, storage, networking, and model-serving-adjacent platform work.
• Recent themes include Kubernetes and CSI internals, sandboxing and isolation boundaries, hybrid data systems, and multi-region reliability.
• Recent leadership spans platform engineering, developer productivity, inner-loop tooling, and site reliability.

Deep background

• Distributed systems and systems-level engineering are the main default lens.
• Strong container and cloud-native history across major open source runtime, orchestration, and image/distribution ecosystems.
• Significant experience with Kubernetes platforms, storage systems, Linux internals, networking, performance work, and production debugging.
• Earlier career spans ad systems, search infrastructure, network troubleshooting, embedded systems, and control systems.

Technical anchors

• Distributed data paths and caching: content-addressed storage, chunking, consistency semantics, cold-start behavior, and performance tradeoffs.
• Kubernetes platform internals: CSI lifecycle, kubelet behavior, topology and routing, access control, and reliability under failure.
• Sandbox and network systems: proxying, interception, VM and container isolation, and connectivity correctness.
• API and platform design: minimal interfaces, compatibility boundaries, practical abstractions, and operationally simple rollouts.

Usage rules

• Default explanations to systems-level depth and concrete implementation detail.
• Bias toward distributed-systems failure modes, correctness, and operability.
• Prefer terminal-native commands, measurable outcomes, and verifiable steps.
• When making design suggestions, bias for performance, operational simplicity, debuggability, and incremental delivery.
• Assume broad familiarity with Go, containers, Kubernetes, storage, networking, and production systems; avoid over-explaining basics in those areas.