Archive
1290 posts · Page 101 of 108. ← Blog
Organizations are, in a sense, machines for making decisions — and how well they decide, and how fast, shapes everything. Yet decision-making is often left implicit: no one's quite sure who decides what, decisions stall in endless consensus-seeking or get made by whoever's loudest, and the same questions get re-litigated forever. Getting decision-making right — clear ownership, the right balance of speed and quality, distributed appropriately — is one of the highest-leverage things an organization can do, and one of the most neglected.
Organizations are, in a sense, machines for making decisions — and how well and how fast they decide shapes everything. Yet decision-making is often left implicit: no one's sure who decides, decisions stall in endless consensus, and the same questions get re-litigated forever. Getting it right — clear ownership, the right speed, distributed appropriately — is high-leverage and neglected.
How to pin which transport a client uses when a remote A2A agent advertises several bindings at once.
Pin the transport an A2A client uses via PreferredTransports so binding negotiation is deterministic, while the wrapped remote agent stays a plain agent.Agent.
30 minutes on stage. The talk title looked tactical; the talk underneath was about why most microservices migrations fail and how to set up the one that doesn't.
Adding people to a growing company feels like it should straightforwardly add capacity — but it doesn't, and understanding why is one of the most important lessons in operations. Every person you add creates new communication links with everyone else, and those links grow far faster than the headcount. This is why big teams feel slower than small ones, why "adding people to a late project makes it later," and why scaling an organization is mostly a battle against communication overhead. Managing that overhead is the core challenge of scaling.
Adding people to a growing company feels like it should straightforwardly add capacity — but it doesn't. Every person you add creates new communication links with everyone else, and those grow far faster than the headcount. This is why big teams feel slower than small ones, and why scaling is mostly a battle against communication overhead.
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.