Skip to content

EJENGINEERING JOURNAL

Notes written to the same standard as the code.

Long-form entries on systems that appear in the evidence — what was decided, what it cost, and what broke along the way. Sources linked throughout.

  1. NO. 0012026-07-02

    Lessons from publishing a negative result

    Helios-Dx set out to find a quantum advantage for privacy-preserving medical inference. It found none. What closing a study honestly — capacity-matched, seeded, citable — taught me about engineering discipline.

    7 MIN#research #integrity

  2. NO. 0022026-07-02

    Designing concurrent inventory systems

    One invariant — stock is never oversold — defended through idempotency keys, a Redis queue, and a row-locking Postgres transaction. Why the queue exists, why optimistic locking wasn't enough, and what it cost.

    9 MIN#backend #concurrency

  3. NO. 0032026-07-02

    Hidden-state geometry for LLM security

    Text filters read what attackers write. GEOFENCE-LLM reads what the model does: trajectory geometry across layers, windowed features, and a fail-closed authority — plus the honest numbers that keep it a research direction.

    8 MIN#llm-security #interpretability