Archive
1046 posts · Page 53 of 88. ← Blog
How a whole workflow binds as a single executor inside a larger workflow, so pipelines compose two levels deep.
inproc.BindSubworkflowAsExecutor binds a whole workflow as one node; an order pipeline nests Payment and FraudCheck two levels deep, and inner events still bubble up.
A guardrail that blocks a run before the model, chained ahead of a logger — and the upstream nil-update panic I fixed along the way.
A guardrail middleware that blocks an Microsoft Agent Framework Go run before the model, chained ahead of a logger — plus the tool-approval nil-update panic I fixed upstream in PR #472.
The funnel has a hidden flaw as a mental model: it's a leaky bucket you must keep refilling from the top, forever. Growth marketing's key insight is to look for loops instead — mechanisms where the output of using the product feeds back into acquiring more users, so growth compounds rather than requiring ever-more input. Combined with an experimental, data-driven mindset that engineers take to naturally, this is how modern products grow systematically rather than by pouring money into the top of a funnel.
The funnel has a hidden flaw: it's a leaky bucket you must keep refilling from the top forever. Growth marketing's key insight is to look for *loops* instead — mechanisms where using the product feeds back into acquiring more users, so growth compounds. Combined with an experimental mindset engineers take to naturally, it's how modern products grow.
How type parameters and constraints actually work in Go 1.18+ — writing functions and data structures that are type-safe across many types, when the compiler can infer type arguments for you, and the harder question of when a plain interface is still the better tool.
How type parameters and constraints actually work in Go 1.18+ — writing functions and data structures that are type-safe across many types, when the compiler can infer type arguments for you, and the harder...
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.