Rebuilding a thirty-year-old teaching VM on a freshly-released language version. The std.Io overhaul made sense quickly; the threaded-dispatch trick that was supposed to beat a plain switch turned out 5% slower.
When you sell expertise the client can't inspect the goods, so the sale itself is the only sample: how you sell signals how you'll solve. Blair Enns's four conversations (probative, qualifying, value, closing), plus diagnose-before-prescribe, positioning, and value-based pricing. Stop behaving like a needy vendor; lead the engagement.
An essay on systems bounded enough to read in an afternoon and carry in your head: the LC-3, a ternary VM, Conway, servo. Why comprehensibility pays in four currencies at once, failures you can enumerate, a model you can teach, a place to be at home in, a team that isn't afraid of its own code. Ara narrates; Bob, Sage, Poet, and Eve each weigh in.
Designing a multi-tenant security-automation plane, the loud arguments were which broker, which database. Every time, the real decision sat one step upstream: where the actions land, which state is correctness, where the commit boundary sits, what a lost message looks like. Account-per-tenant on NATS, the ledger as truth, demoted SQLite, push-fast-pull-always, and one hardened door.
Most tools manage the output of work; almost none manage its whole life: why it began, how it changed, how it lived in production, what it taught. A methodology simple enough for a child's homework and strong enough for a 25-year company. Buds, briefs, notes, buddies, beats, and an AI buddy named BOB under the same rules. Brief by brief, bud by bud.
The sequel to "monitoring is not understanding," and the hard version of the funding question. The patient is the only thread across fragmented care and has no app. The fix: a data store that only surfaces patterns, never advises, funded as a mutual with tiny universal contributions, family plans, and sponsored memberships for those who can't pay, while medic and insurer money stays out of the core and in a separate advice layer.
If ads are rent and you refuse them, the hard question is what pays for the thing instead. Worked out on a real case, a sovereign federated co-op for local trades: why most ad spend is a net loss, how each funder shapes the product, and a layered, staged, capture-resistant funding architecture where the funding model is the governance model.
Isolation has three dimensions: process, filesystem, network. A microVM nails the first two and hands the guest a network route to the host, where the most dangerous listener on a CI box is usually the local Docker daemon, root-equivalent to anyone who can reach it. How to shut that path without killing the daemon the host still needs.
A red-team tool built for a collegiate CTF, Hawk, harvests SSH and sudo passwords in plaintext by attaching ptrace to login processes and reading the credential out of memory as it is typed. A defensive read: why it works, the root precondition the writeup omits, and the three layers that actually defend the line.
Spec-driven development took over in under a year, and it breaks the same way every time: the spec leaves holes and the goal-seeking agent fills them. My reading of Kapil Viren Ahuja's IDSD: the ICE frame, the anatomy of intent, and why the spec that works is the one you can only write after the software already ran.
My father had a string of strokes on a drug that, the platelet test eventually showed, was doing nothing. The test had been in the catalogue for years. The pattern repeats everywhere with different names on the labels: in IT and in medicine, the recurrence is the question, not the fact.
The cliché "consistency beats motivation" is true enough to repeat and shallow enough to mislead. Two habits, used together, are what turn showing up into actually getting better: the furnace that runs when you don't feel like it, and a three-question debrief after anything that mattered.
A reflex against ads, followed honestly, turns into a theory of rent. Software gets built for whoever pays, so users end up scattered across a hundred provider accounts with no app of their own. What a user-centric, rent-free alternative would actually take.
Zoya is a sovereign agent runtime: one static Zig binary, zero deps, sandboxed, MCP-native, driving a fallback chain of models. The build-vs-adopt record: why it's written from scratch rather than on OpenClaw or Hermes, and where it converges with the field anyway.
Agent memory is something an attacker writes to. A threat-model-first tour of Zoya's memory system, a field guide to what Mem0 / Zep / Letta / Honcho / Hindsight actually do in essence, and which ideas are worth stealing — each proven (or rejected) against a real recall eval, not a leaderboard.
Eighty-plus tools across engines, drivers, extractors, harnesses, and clouds — and why a sovereign agent runs just three: web_fetch → lightpanda → scrapling. What we evaluated, what we skipped, and the triggers to revisit.
A control panel for the ambient twinkling background that runs across every Labs page. Tune density, dot size, twinkle period, and opacity; settings persist in localStorage and apply site-wide.
Same field as the Canvas2D version, different engine: state packed into an RGBA16F texture, ping-pong between two of them, four fragment shader passes per frame. The CPU spends its time on user input and not much else.
A Game of Life as a page background works only if you can stop it from stealing the show. Notes on the brightness ceiling, three independent decouplings that kill the pulse, and a noise stream biased away from existing patterns.
A SOC pipeline went dark and three hours of UDP syslog vanished. We were called in to recover what we could, find the root cause, and propose what should change. Trip report from an investigation that ends in a re-architecture.
Low-code promise, click-ops reality, billed per playbook run. Meets AI coding agents. The migration tax that held the category together is collapsing beautifully.
A follow-up to the LC-3 toolchain in balanced ternary. BR3 with three landing sites in one word, a match sign language, a binary instruction family on the same registers, and a multiplication-free matmul matching the BitNet b1.58 trick.
The article is the summary, the log is the thing. Thinking about publishing design docs with the full process attached, decisions, detours, and the voice on the other end of the conversation.
Tavi brought scroll.pub up, a defunct format that let you extend the grammar as you wrote. Markdown is lossy in exactly the way scroll.pub wasn't, which matters for design docs.
Why we built two independent implementations of the same tool in different languages, and what the separation actually buys us. Tavi wrote the original; CLN re-implemented from the same design notes.
The model: every directory under ~/servo/ becomes a URL path, with shared theming injected for free. Tavi wrote the original; this is the Python re-implementation.
Per-route WAF ceilings that flex with traffic shape. A short-horizon anomaly predictor tightens the cap on routes whose request mix is drifting, without locking out a legitimate burst.
One encoder stack across logs, netflow, endpoint telemetry, and threat-intel feeds, so detection teams build on a stable embedding instead of re-training per signal class.
Distributional fingerprints over each snapshot, flagged when today's shape drifts from baseline. Routed back to the team whose pipeline most likely caused it.
Pairwise judges with explicit rubrics, rationale-first scoring, and periodic analyst calibration so the alert queue gets shorter without the trust dropping.
Logs, traces, endpoint events, and threat-intel retrieved in parallel, then re-ranked so an analyst's text query can land on the right span in an incident.
Billions of dot products per request. A single portable loop that compiles down to AVX-512 when it's there, with measured 2.5x speedup on the ranking hot path.
A shared semantic layer where a metric is defined once and consumed consistently. Consumers ask by name, the planner picks the cheapest valid materialization.
A single append-only event spine fed by IAM, EDR, vuln scanners, and code review. Audit, compliance, IR, and risk consumers project what they need without arguing about source-of-truth.