1046 posts · Page 50 of 88. ← Blog
Modeling borrower hardship as an explicit state machine, so relief, delinquency, and accounting never disagree.
Modeling hardship: payment holidays, term extensions, re-aging, and how restructuring interacts with delinquency and accounting.
Lay out a two-tier retail CBDC — central-bank ledger, intermediaries, retail wallets, and the offline mode that makes engineers nervous.
Lay out a two-tier retail CBDC: central-bank ledger, intermediaries, retail wallets, and offline modes.
Instrument auth rate, settlement lag, and decline-reason breakdowns instead of raw uptime.
Instrument the payment SLOs that actually matter: auth rate, settlement lag, and decline-reason breakdowns.
Protect PINs with DUKPT key-per-transaction derivation and point-to-point encryption all the way to the HSM.
Protect PINs with DUKPT key-per-transaction derivation and point-to-point encryption to the HSM.
Post 18 of 26 in "Google ADK, Concept by Concept" — retrieval tools, grounding metadata, rendering citations, and the retrieve→augment→generate loop.
Grounding answers in real data: retrieval tools, grounding metadata returned with responses, rendering citations from that metadata, and the retrieve-augment-generate RAG pattern in ADK.
How one router function plus a `path_map` dict lowers to exactly one edge firing per step.
A conditional edge is a router function plus a path map: the router reads state and returns a key, the path map turns that key into the next node. This is how branching (and, next post, loops) are expressed.
The final lesson ties the whole Go tutorial into one small product: an assistant that answers questions about your docs — grounded, cited, and refusing to guess.
The capstone: a grounded DocQA agent that answers only from embedded docs via a search_docs tool, cites sources, and refuses to guess — with an optional reviewer.
Agents as graph executors in Go: switch routing, fan-out/fan-in barriers, and mixing typed function nodes with agent nodes.
Agents as Go workflow executors: switch routing, fan-out and fan-in barriers, and mixing typed function nodes with agent nodes in one graph.
The income statement is the one financial document every engineer should be able to read, because it's the scoreboard everyone above you is watching. It answers, for a period of time, the most basic business question — did we make money? — but the real value is in its structure: the journey from "money customers paid us" at the top to "profit we actually kept" at the bottom, with every cost that eats into it along the way. Once you can read that journey, a huge amount of business behavior stops being mysterious.
The income statement is the one financial document every engineer should be able to read — it's the scoreboard everyone above you is watching. The real value is in its structure: the journey from 'money customers paid us' at the top to 'profit we actually kept' at the bottom, with every cost that eats into it along the way.
What a goroutine actually is, why it is cheaper than a thread, and the one rule that separates working concurrent code from a program that quietly leaks itself to death: every goroutine you start must have a way to stop.
What a goroutine actually is, why it is cheaper than a thread, and the one rule that separates working concurrent code from a program that quietly leaks itself to death: every goroutine you start must have...
How a single loan payment is split across fees, interest, and principal — and why the engine that does it has to be deterministic, auditable, and safe to run twice.
How a loan payment is split across fees, penalties, accrued interest, and principal, with configurable waterfalls and partial-payment rules.
Design MPC / threshold-signature custody so no single party or HSM holds a whole key.
Design MPC / threshold-signature custody so no single party or HSM holds a whole key.