I'll keep this simple. My name is Vondray Sanford. I'm a software engineer with over seven years of experience building enterprise systems, and this is the first post on my blog. I'm starting this blog because I'm deep in work that sits at a new super exciting intersection, enterprise .NET systems and modern AI engineering. I want to document what I'm learning, building, and shipping in real time.

Who I Am

My core stack is C#/.NET, React, TypeScript, SQL Server, and Azure, that's where most of my professional experience lives. I've spent years building full-stack enterprise data applications, the kind of systems that move enormous volumes of high-stakes data every single day. The scale is real, and the stakes are high when your data pipelines feed into decisions worth billions.

Before that, I maintained and extended systems at a massive manufacturing plant, supporting thousands of daily users across the facility. When something broke at that scale, you heard about it FAST. That experience taught me a lot about writing software that actually holds up under pressure, not just software that works on your local machine.

One project I'm particularly proud of is building a bulk admin tool that reduced monthly support tickets by 90%. That was built as a result of just paying close attention to where the pain was and building the right solution. Those are the kinds of problems I like solving, the ones where good engineering directly eliminates friction for real people.

I'm a lifetime member of the ACM, a member of GDG Atlanta, and a member of NSBE. I care about the craft, and I care about the communities around it.

What I'm Working On Now

Over the past year, I've gone deep on AI engineering. Not just experimenting with APIs, but building applications and infrastructure around it. I have worked on an AI-powered evaluation service at work using ML integrations. I built AI-driven PR review and change request automation that's now used by more than a hundred engineers across the organization. These are real production systems doing real work.

On my own time, I've been building projects like DocQuery, a RAG application that lets you query your own documents using retrieval-augmented generation, and SparkBench, a benchmarking suite I wrote specifically for the NVIDIA DGX Spark. I run local LLM inference on a DGX Spark at home, and having that kind of compute on premises changes how you think about AI development. It's way more enjoyable to only have to worry about running the model instead of waiting on API rate limits or worrying about sending sensitive data to a third party.

I did some research early on into multi-agent workflows and orchestration patterns, and that's become a major area of focus. Composing multiple specialized AI agents into a pipeline that handles complex tasks like code review, document analysis, and data processing is where I think enterprise AI is heading. I'm building toward that.

What This Blog Will Cover

This blog sits at the intersection of enterprise .NET development and modern AI engineering. That means you'll see posts about:

AI Engineering: RAG architectures, multi-agent workflows, local inference, embedding strategies, prompt engineering patterns that work in production.

Enterprise .NET: C#/.NET patterns, SQL Server optimization, Azure infrastructure, the kind of architecture decisions that matter when your system serves thousands of users and processes terabytes of data.

Infrastructure & DevOps: Docker, Kubernetes, CI/CD pipelines, and the lessons learned from debugging things like file path differences between Windows and Linux containers (I've got stories lol).

Side Projects: Honest write-ups on what I'm building, what's working, what isn't, and why I made the decisions I made.

Technology News That I Find Interesting: My take on what's happening in AI and the .NET ecosystem, filtered through the lens of someone who has to ship things with this stuff, not just post about it.

I'm not going to write posts full of vague advice. If I'm writing about something, it's because I've integrated it, built it, debugged it, or shipped it. I'll share code, architecture decisions, and the reasoning behind them. If I don't know something, I'll say that too.

On to the Real Stuff

That's the introduction. Now you know who I am, what I work on, and what to expect from this blog. I'll be publishing regularly with new posts on AI engineering, .NET architecture, infrastructure, tech news, and whatever I'm building next.

If any of that sounds interesting, stick around! First real technical post is coming soon.