Start with the real workflow
The request is not always the problem. I look at how the work is actually performed before deciding what to build.
About
Full-Stack Software Developer
I build practical applications around real workflows. My work spans Blazor, ASP.NET Core, APIs, SQL Server, Azure hosting, IIS, application architecture, interface design, and production support.
Building scalable business software, workflow platforms, and practical tools with .NET, Blazor, SQL Server, and Azure.

Background
My path into software was not a traditional computer-science route. I earned a bachelor's degree in art and also completed coursework toward a robotics minor. After college, I realized software development brought together the things I cared about most: creativity, technical systems, problem-solving, and the ability to turn an idea into something useful.
I built my software career through certifications, professional programming training, independent study, and years of hands-on production work. The art background remains a practical strength in interface design, visual communication, creative problem-solving, and product presentation. My robotics coursework reflects a long-running interest in how technical systems fit together.
How I approach problems
Sometimes the request is clear. Sometimes someone only knows that a process is frustrating. In those situations, I prefer to see the work firsthand, understand why each step exists, and determine whether the best solution is to automate the process, simplify it, or eliminate an unnecessary step entirely.
I look for the friction people have stopped noticing. A request to track an item today may become storage, movement, history, reporting, approvals, sales, or another stage of its lifecycle tomorrow. I do not believe in overengineering every solution, but I do believe in understanding where the workflow is likely to grow before choosing an architecture.
Development philosophy
The request is not always the problem. I look at how the work is actually performed before deciding what to build.
The architecture should meet the immediate need without turning the next useful feature into a rewrite.
I connect the interface, API, database, hosting, security, and support needs into one dependable product.
Tedious work, repeated waiting, and unnecessary manual steps are opportunities to make someone's day better.
Professional experience
Confidential platform work
A widget-driven portal system that grew from a simple hosting concept into a reusable website and application builder.
The original requirement was to host customer portals through a website. I helped develop the idea into a configurable platform where reusable widgets can be assembled into different customer experiences. Individual widgets can be as small as a content block or as substantial as a complete business feature.
Production manufacturing work
I have worked directly on software that tracks material movement between manufacturing departments. These systems had to account for inventory state, chemical requirements, safety restrictions, and production-affecting data changes.
Work in this environment reinforced the importance of validation, traceability, data integrity, and understanding how a change in one workflow can affect the entire operation.
End-to-end ownership
My role rarely stops when the code compiles. I work across the application lifecycle so the system can move from a real requirement to dependable production use.
Independent platform work
“Manufacturing taught me that every department solves a different problem—but none of them work in isolation. TITAN Core was built so the software wouldn't either.”
TITAN Core is my largest and most personally meaningful independent software project. I designed it as a reusable, modular manufacturing platform for different departments and sites—not another collection of rigid, disconnected applications.
The modules shown on this site are functional application modules, not conceptual mockups. See the TITAN Core case study.
Creative exploration
Game development is my newest independent area of exploration and a creative technical outlet. It gives me a different medium for building reusable systems: save frameworks, modular room-placement and building tools, gameplay features, and editor utilities.
It is an active area of learning and experimentation, grounded in the same platform thinking I bring to business software.
Capabilities
What comes next
I want to continue growing as a hands-on senior software developer. I enjoy technical ownership, architecture, mentoring through code review, and helping shape products, but I am not pursuing a management path.
I do my best work in teams where developers have meaningful ownership, work closely with users, and can directly influence the quality and direction of the product.
Open to discussion
I am interested in hands-on Senior Software Developer opportunities where I can own meaningful systems, work closely with users, and continue building.