1290 posts · Page 77 of 108. ← Blog
Designing a closed-loop wallet from the ledger up: double-entry balances, the money lifecycle, safeguarding client funds 1:1, and the engineering that keeps top-ups, holds, and reconciliation honest.
Designing a closed-loop wallet: top-up, hold, spend, refund, safeguarding of e-money, and the double-entry ledger behind a balance.
How to aggregate balances, compute target-vs-actual, and fire cutoff-aware sweeps that keep settlement accounts solvent without stranding idle cash.
Teaches how to engineer treasury liquidity: multi-account balance aggregation, target-balance and zero-balance sweep rules, cutoff-aware transfers, and intraday funding checks to keep settlement accounts solvent.
How price-time priority, a single-threaded sequencer, and gap-free event streaming combine into an exchange core you can replay byte-for-byte.
Teaches how to build a deterministic matching engine: price-time priority order book, limit/market/IOC/FOK order types, single-threaded sequencer for determinism, and gap-free trade/execution event streaming.
How to architect wallet tiers, HD-derived deposit addresses, HSM/MPC signing quorums, and sweep flows so no one key, and no one person, can move funds.
Teaches how to architect custody: hot/warm/cold wallet tiers, HSM or MPC key custody, withdrawal approval quorum, address derivation (HD wallets), and sweep flows from deposit to cold storage.
State remembers things inside one chat; Memory is the searchable archive that lets an agent recall what you told it weeks ago.
Memory is long-term recall across sessions, distinct from per-session state: MemoryService stores and retrieves prior context, surfaced via a recall tool so an agent remembers a user over time.
How to express the classic MapReduce word-count as a five-stage workflow graph — fan-out to mappers, barrier to a shuffler, fan-out to reducers, barrier to completion.
MapReduce word-count as a five-stage workflow: fan-out to mappers, barrier to a shuffler, fan-out to reducers, barrier to completion, coordinated via shared state.
Five prebuilt multi-agent shapes — Sequential, Concurrent, Group Chat, Handoff, Magentic — and when each beats hand-wiring a graph.
Sequential, Concurrent, Group Chat, Handoff, Magentic — the five prebuilt Microsoft Agent Framework orchestrations in Python and when each beats hand-wiring a graph.
Forecasting the future from the past is one of the oldest and most valuable things data can do — predict demand, traffic, revenue, load, prices. But time-series data breaks the assumptions most machine learning is built on, and treating it like ordinary data is the fastest way to build a forecaster that looks great in testing and fails in production. This series builds forecasting from first principles, starting with why time is different.
Forecasting the future from the past is one of data's oldest, most valuable jobs — but time-series data breaks ML's i.i.d. assumption (order matters, observations are dependent, the data is non-stationary). Why that dependence makes forecasting both possible and hard, and the vocabulary (trend, seasonality, noise, stationarity, horizon).
Everything in this series has been building toward a single approach to sales — one that finally makes selling something an honest engineer can respect and do well. It goes by names like consultative selling and solution selling, and its premise is simple: stop selling products and start solving problems. The salesperson becomes less a pitchman and more a trusted advisor who understands the customer's problem and helps solve it. This isn't just nicer; it's more effective, and it's the modern standard for anything beyond a simple transaction.
Everything in this series builds toward a single approach to sales — one an honest engineer can respect. It goes by names like consultative and solution selling, and its premise is simple: stop selling products and start solving problems. The salesperson becomes a trusted advisor, and this isn't just nicer — it's more effective.
A working guide to Python's function signatures — positional and keyword arguments, default values and the mutable-default trap, arbitrary-argument packing and call-site unpacking, keyword-only and positional-only parameters, and treating functions as first-class values.
A working guide to Python's function signatures — positional and keyword arguments, default values and the mutable-default trap, packing with *args/**kwargs, unpacking at call sites, keyword-only and...
What a Go pointer actually is, why there's no pointer arithmetic, `new(T)` versus `&T{}`, the addressability rules that decide what `&` will even compile against, and when reaching for a pointer helps versus when it just adds indirection and GC pressure.
What a Go pointer actually is, why there's no pointer arithmetic, `new(T)` versus `&T{}`, the addressability rules that decide what `&` will even compile against, and when reaching for a pointer helps...
How Original Credit Transactions move money onto a card in near real time — and why pushing is a different animal from pulling.
How OCT/push-to-card (Visa Direct, Mastercard Send) moves money to a card in near real time, eligibility/limits, and reversal handling.