Enterprise Agents Will Compete on Graph Engineering
Enterprise agents need governed relationships between people, data, permissions, memory, and workflows not just better retrieval.
I write about building software, engineering leadership, AI, and what worked in practice.
Enterprise agents need governed relationships between people, data, permissions, memory, and workflows not just better retrieval.
Building a useful autonomous AI teammate is less about the chat interface and more about routing, trust, memory, governance, and workflow reliability. We built a marketing operator to understand this better.
What leading engineering at an NGO taught me about constraints, field research, and small experiments.
One team consistently shipped on time without weekend work. Here's what they did differently.
As agents move into real workflows, the org chart is coming out with the same boxes and different arrows: who depends on whom, where review time goes, and which skills matter more.
Advice from building enterprise-grade agent systems on why the morning brief is the best first agent to ship, what teams get wrong, and the design rules that make people trust it.
The first useful agent in a company is often the one that reconstructs context and gives people a better starting point.
Engineering decisions are bets under uncertainty. Strong teams optimize for probabilities, learning speed, and reversibility.
A practical look at using a compact UI DSL to reduce LLM token overhead, improve structure validation, and compile cleanly to JSX.
AI has expanded engineers’ reach across the stack but the winners will be the ones who can verify, debug, and operate systems end-to-end.
From server-first rendering to no-JS fallback and cross-browser checks.
Implementing highlight-to-annotate using WebLLM for in-browser inference.
The real measure of engineering leadership isn't what you shipped. It's what keeps working after you leave.
Vibe coding can create false velocity, and negatively impact young engineers.
Chat bots help when goals are ambiguous, but they introduce context switches.
How I built a cross-functional web platform team while replacing a legacy frontend.
What changed when I moved from writing code to building a team that could make decisions without me.
Most of our failed projects died from bias and misguided assumptions, not bad engineering.
How Pkl Language Improved Our UI Builder.
We drifted from our users, and our product showed it. Raw WhatsApp messages fixed what dashboards could not.