I’m Adarsh Mishra, a Staff Engineer at Qube Cinema. I work at the boundary between remotely deployed systems and cloud services—distributed agents, observability, safe updates, and recovery.
I also build production media infrastructure across Go, Rust, C++, Linux, Kubernetes, GStreamer, and GPU rendering.
Making remote software observable, recoverable, and safe to update.
| System | Signals | Runtime | Rule |
|---|---|---|---|
| distributed control | traces · logs · metrics | Go · Linux · Windows | rollback is a feature |
I’m most interested in software that has to keep working through unreliable networks, partial failure, operational constraints, and long-lived deployments.
| Area | What I care about | |
|---|---|---|
01 |
Distributed systems | Queues, delivery semantics, recovery, and the contracts that keep remote systems dependable. |
02 |
Cloud & observability | Kubernetes, OpenTelemetry, production diagnostics, and evidence-driven incident analysis. |
03 |
Platform engineering | Safe updates, rollback, packaging, and services that survive real operating environments. |
04 |
Media infrastructure | Secure playback, GPU rendering, and the systems behind modern digital cinema. |
Explore the systems in detail ↗
- Failure-aware by default — design the recovery path at the same time as the success path.
- Evidence closes the loop — traces, tests, and production behavior matter more than a plausible explanation.
- AI with engineering judgment — use agents for leverage; use architecture and verification for confidence.
RealAdarsh/skills is a collection of host-neutral playbooks for coding agents—focused procedures for work where plausible output is not enough.
npx skills@latest add RealAdarsh/skillsask-adarsh
· cpp-to-rust-port
· jj
· reuse-first
· technical-blog-writing
systems Go · Rust · C++ · Java · Python
platform Linux · Windows · Kubernetes · Docker · CI/CD
media GStreamer · wgpu · Vulkan · DCI / SMPTE
signals OpenTelemetry · OTLP · traces · logs · metrics
data SQL · NoSQL · Kafka · Redis
How to preserve behavior, redesign ownership, verify parity, and avoid producing C++ wearing Rust syntax.