Make profiling routine, not just an emergency tool
Standardize how teams capture and interpret profiles (CPU, memory, IO) and convert results into actionable fixes with verification steps.
Create a skill called "Profiling Playbook". Inputs: - The service/component and the symptom (CPU, latency, memory) - Environment where profiling is allowed Output: - A profiling capture checklist (safe and repeatable) - Interpretation guide and common pitfalls - A verification plan for the fix (benchmarks/telemetry)
Profiling is often delayed until crisis. This recipe makes profiling repeatable: capture,
interpret, act, and verify.
Find missing spans and broken propagation in microservice flows
Debug microservices by enforcing end-to-end correlation (trace IDs, request IDs) and systematically locating propagation breaks or sampling gaps.
Make every incident searchable by one ID
Ensure logs, traces, and error reports share correlation IDs so debugging doesn't require "grep archaeology." Adds a baseline instrumentation and logging contract.
Auto-generate proxies the moment footage lands
Choppy playback, laggy scrubbing, and unusable timelines — even on strong machines — often comes down to editing long-GOP or heavy codecs at high resolution without proxies. This recipe generates proxies automatically whenever new camera originals appear, so every project starts edit-ready instead of debug-ready.
Keep media caches from eating your SSD and slowing your apps
Media cache and disk caches balloon over time, causing storage emergencies and performance regressions. This recipe turns cache cleanup from a panic action into a controlled, scheduled maintenance job — for Adobe Premiere Pro, After Effects, and similar tools.