Topical Takes
Short, opinionated posts on eBPF, Linux internals, and the tools we all run in production.
AlleBPF30linux29yeet26observability12AI agents9security7networking4uprobes4claude-code3exectop3kubernetes3supply chain3tcpdump3tracing3audit2bcc2BSON2ci2containers2execsnoop2HTTP2incident-response2MongoDB2process-attribution2processes2802.111agent-security1ai-sre1auditd1biolatency1bpf-verifier1bpftrace1build-performance1capabilities1cgroups1Cilium1CO-RE1confidential-computing1context-switches1cpu-accounting1cryptojacking1egress1exfiltration1integration-testing1kprobes1kworker1local-llm1make1MCP1memory1n-plus-one1nodejs1npm1off-cpu1ollama1oom1opentelemetry1packet-capture1postinstall1prepared statements1proc-filesystem1process-masquerading1production1profiling1query-shapes1Redis1RESP1rf1root-cause-analysis1runqlat1sandboxing1schedstat1slowlog1SQLite1ssh1stratum1sudo1tcp-retransmits1threat-modeling1tunnels1websocket1wifi1wireguard1wireless1wss1
Why Is My Build Slow? How to See What It Is Running Thousands of Times (2026)
A slow build is usually not one slow step. It is a cheap command running per file when it should run once, or a step running twice. Fold every process launch into one row per kind of command to see the counts, and read the fork-to-exec median to separate a slow program from a slow launch.
build-performancemakeciexectopeBPFprocesseslinuxyeet
Read more →See Every Process a Command Starts on Linux in 2026: My Honest Review of execsnoop
execsnoop hands you a firehose: one line per execve(), host-wide, perfect for grep and unreadable when you read it yourself. An honest review of where that shape stops working, and the execve-only and 20-argument limits behind it.
execsnoopbcceBPFprocessestracinglinuxyeet
Read more →