1046 posts · Page 81 of 88. ← Blog
How to drive a slow remote agent that answers with a continuation token, then poll that token to completion instead of blocking on one long call.
Ask a remote A2A agent with AllowBackgroundResponses, get a continuation token, and poll with WithContinuationToken and no messages until the token clears.
Seven cycles. Ten-plus students. Most shipped, a few didn't, all of them taught me something about engineering culture. Notes on what works for mentors and what works for students.
Here is one of the most profound and underappreciated ideas in all of software engineering, and it comes from operations, not code: the structure of your software will end up mirroring the structure of your organization. This is Conway's law, and its implication is startling — if you want to change your architecture, you may need to change your org chart first. Organizational design isn't just an HR concern; for technical organizations, it's an architectural decision. How you organize people shapes what you build.
Here is one of the most profound ideas in software engineering, and it comes from operations, not code: the structure of your software will end up mirroring the structure of your organization. This is Conway's law, and its implication is startling — to change your architecture, you may need to change your org chart first.
How to discover a remote A2A agent's advertised skills and hand each one to a local host agent as an ordinary function tool.
Resolve a remote A2A agent card, turn each advertised skill into a function tool with derived names and descriptions, and hand them to a local Foundry host agent.
What it actually takes to build a unified cloud API library — and why "write once, run anywhere" still doesn't quite work, even for the patterns where it almost does.
Every company has an org chart, and most people treat it as bureaucratic trivia — but the way an organization is structured profoundly shapes how it works: who talks to whom, how decisions flow, what's easy and what's hard, even what the company can build. There's no perfect structure; each common one (functional, divisional, matrix) makes different tradeoffs. Understanding these structures — what each optimizes for and sacrifices — explains a great deal about why your organization behaves the way it does.
Every company has an org chart, and most treat it as bureaucratic trivia — but the way an organization is structured profoundly shapes how it works: who talks to whom, how decisions flow, even what the company can build. There's no perfect structure; each common one (functional, divisional, matrix) makes different tradeoffs.
The other primitive: a directed graph of executors wired by edges, running fully offline with no model, no credential, no Foundry.
Wire two executors into an uppercase to reverse pipeline with the fluent workflow builder and run it fully offline via inproc.Default, iterating ExecutorCompletedEvents.
Every Professional Cloud Security Engineer exam bullet, mapped to a file path in an RBI FREE-AI aligned Go platform. Where the implementation matches, where the analog substitutes, and where the honest gaps are.
"Process" is a dirty word to many engineers — it conjures bureaucracy, red tape, and forms in triplicate. But that's bad process. Good process is simply a repeatable way of doing something that used to require re-figuring-out every time, and it's how organizations stop relying on heroics and tribal knowledge. The real skill isn't avoiding process or worshipping it — it's knowing when a process earns its cost, and keeping it light enough to help rather than smother. This tension, between too little process and too much, is at the heart of operations.
'Process' is a dirty word to many engineers — but that's bad process. Good process is simply a repeatable way of doing something that used to require re-figuring-out every time. The real skill isn't avoiding process or worshipping it — it's knowing when a process earns its cost, and keeping it light enough to help rather than smother.
A custom ContextProvider gives the agent memory: it reads stored facts before a run and learns new ones after — all through the Session.
A custom ContextProvider wires Provide and Store hooks around every run so the agent reads remembered facts before the call and learns new ones after, all in the Session.
The mental model that says no two adjacent layers share a single point of failure for the same class of attack. From TLS to OTel, the eleven layers a customer request crosses before an answer comes back.
Operations is the least glamorous and most underrated function in any company — the invisible machinery that keeps everything running so the visible work (building, selling) can happen. When operations work, no one notices; when they break, everything grinds. As a company grows, the ad-hoc coordination that worked with ten people collapses at a hundred, and deliberate operations and organizational design become the difference between a company that scales smoothly and one that descends into chaos. Understanding operations is understanding how companies actually function.
Operations is the least glamorous and most underrated function in any company — the invisible machinery that keeps everything running. When it works, no one notices; when it breaks, everything grinds. As a company grows, the ad-hoc coordination that worked with ten people collapses at a hundred, and deliberate operations becomes the difference between scaling and chaos.