Archive
1290 posts · Page 100 of 108. ← Blog
The single most common way products fail is also the most avoidable: they solve a problem nobody actually has, or solve a real problem the wrong way, because no one deeply understood the problem first. Engineers and PMs alike are wired to jump to solutions — it's more fun to build than to investigate — but the discipline that separates good product management from expensive guessing is falling in love with the problem, not the solution. Understanding the problem deeply, before building, is where good products begin.
The most common way products fail is also the most avoidable: they solve a problem nobody has, because no one understood the problem first. Engineers and PMs alike are wired to jump to solutions, but the discipline that separates good PM from expensive guessing is falling in love with the problem, not the solution.
How to wrap a plain typed Go function as a tool the model can call mid-run.
Wrap a plain typed Go function with functool.MustNew and attach it via agent.Config.Tools so the model can call it; the SDK infers the JSON schema from the signature.
Status-code-based dispatch made every worker grow a longer and longer switch. Normalising every partner-specific error into an enumerated set let the orchestration logic stop changing as new partners landed.
Product management is one of the most misunderstood roles in tech — engineers often see it as either a glorified project tracker or a mysterious source of demands, and PMs themselves get called "the CEO of the product," which is misleading in the opposite direction. The truth is more specific and more useful: a product manager owns what gets built and why, so that the team builds the right thing. Understanding the role — especially from an engineer's perspective — clarifies a lot about how good products actually get made.
Product management is one of the most misunderstood roles in tech — engineers see it as either a glorified project tracker or a mysterious source of demands, and PMs get called 'the CEO of the product,' which misleads the other way. The truth is more specific: a PM owns what gets built and why, so the team builds the right thing.
How an agent.Session carries conversation history across RunText calls so the model remembers earlier turns.
Thread conversation history across RunText calls with an agent.Session and agent.WithSession, so a follow-up prompt builds on the previous turn; a new session starts fresh.
5K+ loans per month. Three credit bureaus. Multiple payment gateways. The thing that has to be right is the ledger. Notes on what invariants the database enforces vs what the application enforces.
The companies that win over the long run are rarely the ones with the single best idea — they're the ones that execute consistently well, day after day, and keep getting a little better. That's operational excellence: not a one-time achievement but an ongoing discipline of running well and continuously improving. This closing post pulls the series together — processes, structure, org design, scaling, decisions, culture — into the bigger picture of operations as the enabler that lets everything else in a company succeed.
The companies that win over the long run are rarely the ones with the single best idea — they're the ones that execute consistently well, day after day, and keep getting a little better. That's operational excellence: not a one-time achievement but an ongoing discipline of running well and continuously improving — the enabler that lets everything else succeed.
How to wrap every agent run with a middleware — the standard hook for logging, tracing, and guardrails.
Wrap every agent run with an agent.Middleware in the Foundry Go SDK: one pass-through function that observes messages and updates without altering the result.
Borrower onboarding is the most fraud-prone moment in a P2P platform. The shape that worked: deterministic KYC, parallel bureau pulls with fallback, real-time fraud signals, and a maker-checker approval for every disbursement.
Culture is the most powerful and least tangible force in any organization — "the way we do things around here," the invisible set of shared norms and values that shapes how everyone behaves, especially when no one's watching. Every organization has a culture whether or not anyone designed it, and it will either be shaped deliberately or form by accident. Because culture governs behavior at a scale no rules or processes can reach, understanding it — and knowing that it's shaped by actions, not words — is essential to how organizations actually function.
Culture is the most powerful and least tangible force in any organization — 'the way we do things around here,' the invisible norms that shape how everyone behaves, especially when no one's watching. Every organization has a culture whether or not anyone designed it — and it's shaped by actions, not words.
How to resume a long-running remote agent stream after it drops — using a continuation token to reconnect instead of re-sending the expensive query.
Capture the continuation token from a streamed remote run, then reconnect with WithContinuationToken and no messages to resume the same task to completion.
100K+ votes, 10K+ concurrent users during a live AFL Brownlow Medal broadcast. The architecture: Go on Cloud Run, GraphQL + gRPC behind a CDN, vote integrity through Cloud KMS + Security Command Center. Notes on what makes a live-broadcast load shape unusual.