Archive
1290 posts · Page 102 of 108. ← Blog
"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.
One Session threaded through every call turns two stateless one-shots into a single conversation that remembers.
Thread one agent.Session through every RunText call with agent.WithSession to turn stateless one-shots into a single conversation that remembers.
The long-form security narrative for a multi-agent financial assistant — authentication, authorisation, tenant isolation, dual-identity audit, envelope encryption, hash-chained logs, governance, red team, BCP.
Handling user data used to be a technical matter; now it's a legal one, with real regulations, real penalties, and real obligations that engineers build software to satisfy. Privacy and compliance have become part of the job — and, along with the rest of this series' legal basics, they lead to the single most important lesson: legal literacy exists to tell you when you're out of your depth and need a real lawyer. This closing post covers privacy, compliance, and that essential meta-skill. (Educational, not legal advice.)
Handling user data used to be a technical matter; now it's a legal one, with real regulations, penalties, and obligations. Privacy and compliance are part of the job — and they lead to the most important lesson: legal literacy exists to tell you when you're out of your depth and need a real lawyer. (Educational, not legal advice.)
Hand the agent a plain Go function it can decide to call mid-conversation — the model requests it, the framework runs it, the result flows back.
Register a plain Go function as a tool with functool.MustNew; the model decides when to call it, the framework runs it, and the result flows back into the answer.
Board policy as a YAML file the risk team owns. Annexure VI as a database query. Every governance recommendation rendered as a file path in a Go repository.
Contracts run the business world — every deal, job, partnership, and service relationship rests on one — yet most people sign them without really understanding what they're agreeing to. For engineers and founders, a few contracts matter enormously: the employment agreement that may assign your IP, the NDA that binds your confidentiality, the customer contract that defines your obligations. Understanding what contracts are and what to look for turns signing from a blind act into an informed one. (Educational, not legal advice.)
Contracts run the business world — every deal, job, and partnership rests on one — yet most people sign them without really understanding what they're agreeing to. For engineers and founders, a few contracts matter enormously: the employment agreement that may assign your IP, the NDA, the customer contract. (Educational, not legal advice.)
The smallest useful agent: give a model instructions and a name, hand it a message, get a response — collected or streamed.
Build the smallest useful agent from instructions and a model, then run the same RunText call two ways — collected all at once and streamed token-by-token.
Twelve months of running multi-agent AI in a regulated context. SLIs that matter, the incident runbook, drift detection, continuous adversarial testing, secret rotation, compliance posture as code.