explicit state · terminal-first tools · observable failure · measured tails

explore      👀  low-level cool stuff
build        🛠️  focused systems understood end to end
diagnose     🔎  clear cause, clear cost
collaborate  💞️  on low-level cool stuff
believe      ✨  the lone wolf survives, but the pack dies

🧪 My other GitHub: @DrunkenRandomWalker
📫 Open an issue here · LinkedIn

Bid/ask binary-search tree rendered in plain text:

            ------   /
           |21, 32| /
           |21, 21|<
           |  20  | \
            ------   \
  --------   /
 | 20, 20 | /
 |14.1, 21|<
 |  None  | \
  --------   \
                      ----------   /
                     | 19.3, 21 | /
                     |19.3, 19.3|<
                     |    19    | \
                      ----------   \
            ----------   /
           | 19, 121  | /
           |14.1, 19.3|<
           |    20    | \
            ----------   \
                      ----------   /
                     |14.1, 199 | /
                     |14.1, 14.1|<
                     |    19    | \
                      ----------   \
ASK: min 14.1  max 21
BID: max 13    min 10
            ------   /
           |13, 10| /
           |13, 13|<
           |  12  | \
            ------   \
  ------   /
 |12, 10| /
 |10, 13|<
 | None | \
  ------   \
            ------   /
           |10, 21| /
           |10, 10|<
           |  12  | \
            ------   \

This is a separate BST-backed visualization study. The featured engine uses price-indexed FIFO levels plus an occupancy bitset.

redundant feeds · fixed-capacity ring · copy-aware filtering

Three focused exercises at the market-data boundary: merge duplicate and out-of-order feeds into one ordered stream, select large trades without copying their payloads, and suppress unchanged quotes.

Source and scenarios · UDP merger anatomy

single writer · price-time priority · direct cancellation

A deterministic, in-memory matching engine for studying order-book design, failure boundaries, and the operator surface around a hot path.

Implementation and usage · Design and trade-offs

question -> build -> measure -> explain

• Separate machine output from human diagnostics.
• Reconstruct every transition from stable inputs, IDs, and reason codes.
• Measure tails, saturation, drops, and instrumentation overhead.
• Keep terminal views keyboard-first, stable, and readable without color.

JAX / PyTorch for modeling. Ray for parallel execution. Gym for environment contracts. Deterministic runs. Comparable measurements.

All merged upstream:

• ndarray #978 — API ergonomics around shape metadata
• Alacritty #4923 — underline thickness for double-width terminal cells
• Sapling #50 — integration testing for DAG behavior