Leveraging AI to Supercharge Development
Production agentic systems, multi-region consumer infrastructure, and spec-driven AI-native development — built from first principles and shipped as real products.
Tech stack organized by who builds it. Each lab page enumerates the current tech surface — models, platforms, agents, dev tooling — with cross-references into the architectural deep dives below.
Azure AI Foundry, Azure OpenAI, GitHub Copilot, Responsible AI Toolbox.
Vertex AI (Model Garden, Endpoints, Pipelines, Vector Search, Agent Builder) + Gemini multimodal.
GPT-4o, GPT-5, o-series reasoning, Responses API, Realtime, Codex CLI, Swarm agents.
Claude (Opus / Sonnet / Haiku), Claude Code, MCP, Computer Use, Constitutional AI.
Three-layer agentic framework: single-agent loop, multi-agent orchestrator, modular tool SDK.
Multi-region typing platform: voice narration, 7 langs × 9 regions, anycast routing.
AI content factory: spec-driven, RAG, Report Cards, model routing, self-correction.
The managed AI service layer for the post-hyperscaler era — vendor-agnostic, infra-first, BYO-everything. 5 pillars + control plane + 4 deployment envelopes.
Personal RAG, 100% local by default. Drop a folder, ask cited questions from laptop or phone (Telegram bot). MIT-licensed, v0.11.
How I think about LLMs, RAG, agents, and production AI — first principles to shipped systems.
Full production RAG for real verticals — HR, customer transactions, healthcare. Reference architectures end-to-end.
LangChain, CrewAI, AutoGen, LlamaIndex, Pydantic AI — honest comparison with code, pros/cons, and when to pick each.
The open-source low-code canvas for LLM apps and agents (acquired by Workday for their enterprise AI agent platform). Hands-on series — install, build, and database-level observations as I work through real flows.
Wrap your existing REST API as an MCP server in ~60 lines of TypeScript. Three surfaces — REST for developers, MCP for AI agents, CLI for power users — sharing one source of truth. Runnable subscription-status example.
An email inbox rebuilt as a production system — Gmail API, SQLite sender catalog, 4×/day cron, human-in-the-loop over Telegram, Claude Code as the interface. Sender-first triage instead of email-by-email.
The four routing patterns I use in production: rule-based, classifier-based, cascading, parallel adversarial. With the LLM Council pattern — Claude orchestrates, Gemini reviews, Codex validates — for high-stakes tasks.
Your AI vendor is a dependency, not a destiny. Six layers decomposed — the provider gateway, the model-selection decision matrix, guardrails, multi-tenant isolation, and encryption in transit (mTLS) and at rest. Runnable code, animated data-flow diagram.
Langfuse, LangSmith, Braintrust, RAGAS, DeepEval, LlamaGuard — how the industry is adopting LLM observability, evaluation, and safety tooling. Real code for each.
Control plane + data plane + guardrails + observability. Vendor-neutral reference with Microsoft / AWS / custom stack mappings.
25 years across Java, Python, TypeScript, SQL, NoSQL, Kafka, Spring Boot, React, Next.js — and why stack breadth is a multiplier in the AI era.
The production deep dives above represent my core AI-native work. The tabs below cover adjacent areas I actively explore: Onyx RAG prototyping, MCP server patterns, Claude Code excellence techniques, and polyglot AI strategy for multi-model orchestration.
Retrieval-Augmented Generation Systems
Model Context Protocol Implementation
Advanced AI-Powered Development
Multi-Model AI Orchestration
As AI capabilities evolve at breakneck speed, staying ahead means mastering not just individual models, but the art of orchestrating multiple AI systems to create applications that are intelligent, scalable, and cost-effective.