Skip to content

ARTICLES

Technical articles

These notes draw from implementation work on our products. They are pattern essays and failure-mode essays for engineers already working in these areas, focused on design decisions, runtime boundaries, error handling, and the tradeoffs that show up in production systems. Each piece follows a specific problem through to the implementation details that shaped the result.

Qt desktop runtime

  1. C++ - Qt - concurrency 9 min read

    Safe Qt Dispatch Without invokeMethod Soup

    Cross-thread Qt calls get hard to read when every call site spells out raw dispatch mechanics. A small named helper surface makes the policy legible again.

    Read article

IPC and isolation

  1. video - architecture 8 min read

    One Decode Path, Multiple Consumers

    Four consumers of one video stream - preview, detector, recorder, plugin - should not each run their own decoder. What changes when the runtime decodes once and fans the result out, and which failure modes that avoids.

    Read article

  2. IPC - fault recovery 8 min read

    Crash Containment: Treat Stale IPC State as Toxic

    A worker restart is not enough when the host still holds ring buffers, descriptors, and readers bound to the dead process. Why stale IPC state is toxic rather than merely old, and what a recovery contract has to say.

    Read article

  3. plugins - process isolation 9 min read

    One Plugin Contract, Two Execution Modes

    How to keep one plugin surface while the host decides, per instance, whether a plugin runs in-process for latency or out-of-process for crash isolation.

    Read article

UI rendering

  1. visualization - performance 10 min read

    Write Once, Render at Many Zoom Levels

    Live time-series plots age badly when every pan or zoom reduces the full-resolution buffer at frame rate. Pushing aggregation into the writer via a ladder of decimated rings, so the renderer never re-aggregates.

    Read article

  2. Qt - process isolation - UI 9 min read

    A Native Panel in Another Process

    How to isolate a risky UI region in a child process without making it feel like a bolted-on island: pixels up, input down, and no native window embedding.

    Read article