1290 posts · Page 71 of 108. ← Blog
Turning raw blocks and logs into queryable app state that survives reorgs, backfills, and finality.
Building an indexer: block ingestion, log decoding, reorg-safe writes, backfills, and serving queryable balances/history to the app.
Deciding low-value, TRA, and trusted-beneficiary exemptions so low-risk payments stay frictionless while genuine risk gets challenged via 3DS.
Decide PSD2 SCA exemptions (low-value, TRA, allowlist) to keep low-risk payments frictionless around 3DS.
Turn ICT asset and third-party risk, incident classification, and reporting into a system you can actually run — with a resilience-testing loop that keeps it honest.
Engineer DORA operational resilience: ICT asset/third-party risk, incident classification, reporting, and resilience testing.
Classify account tax residency and generate withholding and FATCA/CRS reporting files.
Classify account tax residency and generate withholding and FATCA/CRS reporting files.
How `adk deploy` builds, pushes, and ships an agent in a single step — and the ack-after-invocation rule that keeps event-driven agents reliable.
Deploying an agent: adk deploy with its cloud_run and agent_engine subcommands, containerizing the app, and reliability rules like ack-after-invocation so failures are redelivered, not dropped.
The foundational mental model — why "the graph" is a Pregel program, and how shared state differs from message passing.
LangGraph is shared-state, not message-passing, and both models descend from Google's Pregel/BSP: work advances in supersteps that end at a synchronization barrier. Get this mental model first and the whole API stops being magic.
How one executor stores a value in scoped shared state and later executors read it back — instead of copying a whole payload down every edge.
One executor stores a document with QueueStateUpdate; fan-out counters read it back with ReadState, and an AddFanInBarrierEdge aggregates once both deliver. Offline.
Decoding typed structs from a run, draining a streamed response, and sending an image with `RunMessage`.
Decode typed structs from a run, drain a streamed response by ranging it, and send an image with RunMessage and DataContent.
Knowing the methods is the easy part; building a forecasting system that's accurate, honest, and maintainable is the real job. This closing post assembles the series into practical judgment — how to choose a method, how to ship forecasts that keep working, and the hard-won lessons (start simple, respect baselines, monitor for drift) that no single technique teaches. It turns the series into something you can actually run.
Knowing the methods is easy; shipping accurate, honest, maintainable forecasts is the job. The complexity ladder (naive → classical → ML → deep, stopping when complexity stops helping), the production realities (honest backtesting, calibrated uncertainty, monitoring for drift and shocks), and the hard-won lessons: start simple, respect baselines, stay humble.
Marketing to developers is a special case with its own rules, because developers are the audience most hostile to traditional marketing and most capable of ignoring it. They block ads, skip the sales pitch, distrust claims, and ask other developers instead. Yet developer-focused products get adopted constantly — through a completely different playbook built on substance, authenticity, and respect. If your product's buyers or users are engineers (and if you're reading this, they might be), developer marketing is the discipline that actually works on them.
Marketing to developers is a special case with its own rules, because developers are the audience most hostile to traditional marketing and most capable of ignoring it. Yet developer products get adopted constantly — through a completely different playbook built on substance, authenticity, and respect.
How Go recovers a concrete type from an interface value, why the comma-ok form exists, and the two-word memory layout that explains the single most surprising bug in the language — the non-nil interface holding a nil pointer.
How Go recovers a concrete type from an interface value, why the comma-ok form exists, and the two-word memory layout that explains the single most surprising bug in the language — the non-nil interface...
How a rating engine turns raw usage and transactions into charges — and why the hard part is making that transformation deterministic, replayable, and idempotent.
How a rating engine turns usage/transactions into charges via pricing plans, tiers, and promos, then produces invoices and fee postings.