Vaibhav Attre.boot

retro-futurist workstation init

[ 0.000] POST: workstation bus scan complete
[ 0.013] memctl: 64 GiB addressable, ECC nominal
[ 0.029] sched: run queue initialized
[ 0.041] fs: mounting /home/vaibhav
[ 0.068] net: link up on loopback and uplink0
[ 0.091] ui: terminal compositor ready
[ 0.112] session: entering interactive workspace
Loading command bus, filesystem tree, and process monitor.
Vaibhav Attre.ws
/about/profile
shell bus
vaibhav@ws:/about/profile$ session
interactive workstation online
type `help` or press `/` to focus the shell
tab completes top match
/about/profile

Machine Profile

Grounded systems work across kernels, distributed telemetry, embedded tooling, and ML runtime infrastructure.

readme

I build software where state, failure modes, and performance characteristics matter. That usually means low-level systems, infrastructure with strong operational constraints, or tools that expose what the machine is actually doing instead of hiding it.

The through-line is not a language or a stack. It is a bias toward debuggability, strong interfaces, and evidence-based optimization. I care about the shape of logs, the quality of instrumentation, and the moment when an abstraction leaks under production load.

operating parameters
primary domains
kernels, infra, telemetry, edge systems, ML runtimes
preferred tools
Linux, perf, eBPF, GDB, QEMU, structured traces
engineering style
measure first, simplify interfaces, preserve escape hatches
failure posture
surface state early, design for triage and recovery
bio.log
[trace] built teaching kernels to understand scheduling and VM from the inside.
[trace] worked on telemetry paths where bandwidth and reliability fight each other.
[trace] shipped tooling for embedded and FPGA bring-up when generic tools were insufficient.
[trace] designed runtime controls for ML evaluation and observability pipelines.
current interests
filesystemsvirtual memoryscheduler designembedded observabilitytrace toolingGPU runtimesperformance forensics