20+ years building production systems that solve real business problems
While my recent work has focused on electrical utilities, my core technical expertise spans every industry that needs solid enterprise architecture, cloud infrastructure, and production-grade software development.
Domain expertise may vary, but architectural patterns, development practices, and infrastructure challenges are universal. I've spent two decades mastering the fundamentals that matter in every industry.
Designing systems that scale, integrate, and evolve. From monoliths to microservices, from on-premise to cloud-native, I architect solutions that balance business needs with technical reality.
8 years designing and implementing Azure solutions across compute, storage, networking, and platform services. I understand both the "what" and the "why" of cloud architecture.
I don't just design systems—I build them. From database schemas to REST APIs to responsive UIs, I write production code that ships and maintains itself.
20+ years of Linux/Unix administration, automation, and infrastructure. I'm as comfortable at the command line as I am in Visual Studio.
Two decades of Microsoft technologies means I've seen it evolve from .NET Framework 1.0 to modern .NET 8+, from on-premise servers to Azure cloud-native. I know what works, what's legacy, and how to migrate between them.
I've migrated systems from .NET Framework to .NET Core, from on-premise to Azure, from monoliths to microservices. I understand the challenges of modernization because I've lived them.
While .NET is my primary stack, I'm language-agnostic and framework-flexible. I use the right tool for the job, not just the familiar one.
I've written production code in all of these languages, deployed them, and maintained them over years.
I value working, maintainable, accessibility, and performance over framework hype.
I design schemas, write queries, optimize performance, and understand when NoSQL is actually better than SQL. And, I also know SPARQL and Gremlin, for when graph databases are the right fit.
I automate everything that can be automated, and document everything else.
I believe in sharing knowledge and building in public. My open-source work demonstrates both technical skill and commitment to the developer community.
A comprehensive .NET library for IEC 61970/61968 CIM standards (TC57). Generates strongly-typed C# classes from complex XML schemas, handles RDF serialization, and provides SPARQL query support.
Technical Highlight: This library solves a complex problem—converting massive UML-based standards into usable .NET code. It demonstrates advanced XML schema parsing, code generation, and semantic web integration.
Much of my professional work over the past 20 years has been for clients and is protected by IP agreements or NDAs. While I can't share that code publicly, I can discuss the architectures, explain the technical challenges we solved, and detail why I made specific design decisions. If you're interested in learning more about my client work and the problems I've solved, let's talk.
Before "DevOps" was a buzzword, I was a Unix sysadmin. That foundation—understanding how systems actually work—informs everything I architect and build today.
Almost 20 years working with Linux and Unix systems, from Solaris in the early 2000s to modern Ubuntu, RHEL, and Alpine Linux containers. My daily driver is Arch Linux, and I do a LOT of dotnet development on Linux!
I've configured, deployed, and maintained production servers running everything from web apps to databases to message queues.
If I have to do something manually more than twice, I automate it. Shell scripts, Python CLIs, PowerShell modules—whatever gets the job done.
Understanding systems at the OS level means I can:
I'm as comfortable in a terminal as most developers are in an IDE. Whether it's debugging a production issue via SSH or scripting complex deployments, the command line is where real work gets done. And yes, I do use vim, and I know how to exit it :).
My recent work has been utility-focused, but the technical foundations translate directly to any industry with complex systems and data challenges.
My CAD automation experience (AutoCAD, Inventor API) and understanding of BIM/design workflows translate perfectly to AEC. Building design, construction management, and infrastructure projects all face similar challenges: complex data models, integration between systems, and the need for automation. And I DEEPLY understand the importance of document management and I am quite familiar and comfortable with the Autodesk Vault API as well as Autodesk Platform Services and Autodesk Construction Cloud.
Whether it's financial services, healthcare, manufacturing, or retail, enterprise systems need the same things: reliable architecture, secure APIs, scalable databases, and maintainable code. That's what I've been building for 20 years.
Any organization moving to Azure or building cloud-native applications needs architects who understand both the platform and the migration path. I've done it, documented it, and can teach it.
My GraphRAG research and Azure OpenAI experience applies to any industry exploring AI. Whether it's customer service, document processing, or decision support, the patterns are universal.
Organizations struggling with data integration, knowledge management, or complex reporting need architects who understand data modeling, ETL, and both SQL and NoSQL databases. That's my wheelhouse.
My open-source work and deep technical experience make me well-suited for building developer tools, SDKs, libraries, or platforms that other developers will use. I understand what makes tools usable.
I don't write throwaway demos or proofs-of-concept. Every system I build is designed to be deployed, monitored, maintained, and evolved over years. That means proper error handling, logging, testing, and documentation.
I'm not dogmatic about technology choices. .NET for enterprise backends, Python for data processing, React for rich UIs, Blazor for .NET shops. The decision should be driven by requirements, not preferences. What I don't know today I will learn tomorrow if it makes sense for the clients needs.
Proven, stable technologies beat bleeding-edge every time in production. I stay current with modern practices, but I value reliability over novelty. Your business doesn't need hype; it needs solutions that work.
Architecture decisions, API contracts, deployment procedures, troubleshooting guides—if it's not documented, it doesn't exist. Future developers (including future me) will thank you. I write code like the person who maintains it has violent tendencies and knows where I live, and I teach others to do the same.
Security isn't a feature you add later; it's a foundation you build on. From secure coding practices to proper authentication/authorization to infrastructure hardening, security is non-negotiable.
Users shouldn't wait. Whether it's database query optimization, caching strategies, or asynchronous processing, I design systems that respond quickly and scale efficiently.
Whether you're modernizing legacy systems, building cloud-native applications, or exploring AI integration, I bring 20+ years of production-proven expertise to help you succeed.