§ 00 · What I do
What I do
Six kinds of work, at Auxiliobits and before it. Most AI features end up needing several of them at once.
- 01
AI agents and workflows
Agents that carry out business workflows. It's my day job at Auxiliobits, and at Vtopia I built multi agent pipelines for content generation and user onboarding. I start from the process as a person runs it today, then work out which steps need a model and which stay as regular code.
Covers
- Business process automation
- LangGraph for state and recovery
- LangChain, AutoGen and CrewAI
- OpenAI and Anthropic APIs
- Agents for business workflows
- 02
Tools and MCP servers
Connecting agents to the systems and APIs a company already runs, through MCP servers and function calling. Each tool gets a clear name, a plain description and the fewest permissions that still do the job, because a model will use whatever it's given.
Covers
- MCP servers for company systems
- Function calling
- Integrations with company APIs
- Tool permissions and limits
- 03
Evals, tracing and guardrails
I test agent behaviour with evals, trace runs, and use guardrails to control what reaches users. Without that, nobody can say whether the last change made an agent better or worse. It's also how I find out an agent is wrong before a user does.
Covers
- Evals on the cases that matter
- Tracing agent runs step by step
- Guardrails on what reaches users
- Checks before a change ships
- 04
Backend
I build services for the day they're under load, with queues in between and a cache where reads are heavy. At Jewelnme I architected the whole backend, from product and inventory services to order delivery. At Chaincode it was NestJS microservices in Docker on AWS, behind Nginx.
Covers
- NestJS and Express on Node.js
- REST and GraphQL APIs
- Kafka and NATS between services
- PostgreSQL, MongoDB and Redis
- Docker on AWS EC2 behind Nginx
- Payments with Razorpay and PayU
- 05
Frontend
Interfaces that show what the system is doing while it works. Responses stream in, each tool call is visible as it happens, and errors say what went wrong. People trust an agent they can watch. React and Next.js throughout, with Three.js when a product needs 3D.
Covers
- React and Next.js, app router first
- Streaming responses and tool call UI
- Real time features over WebSockets
- Dashboards with React Query and Highcharts
- Tailwind, React Spring and Three.js
- 06
Technical leadership
At Vtopia I was tech lead over frontend, backend and design, from architecture to launch, and I still wrote code. The standards, sprint process and code review I set up there made the team faster. At Jewelnme I mentored junior developers and led system testing.
Covers
- Architecture and technical direction
- Engineering standards and code review
- Sprint process and delivery
- Mentoring junior developers
- System testing before release
Starting somewhere
If you have an agent demo that only works on a good day, send me a note. That's my favourite kind of conversation.