Technical work across web systems, cross-platform applications, automation tooling, interface implementation, and engineering delivery workflows. The emphasis is on architecture, usability, maintainability, and production-minded execution.
This section highlights the technical side of my work: system structure, implementation quality, automation capability, and cross-platform delivery. It is intended to show how I think about building products, not just listing repositories.
Static sites, landing pages, portfolio sites, internal tools, browser-side scripts, and web assets that support positioning, lead capture, and operations.
Cross-platform application thinking across Flutter, Python desktop tooling, Windows automation, and workflow helpers for repetitive business tasks.
I often connect APIs, reshape local files, automate repetitive steps, and build practical scripts that remove manual work from real operating processes.
I do not treat software as isolated code. I think about user need, operating constraints, deployment path, maintainability, and how a tool fits the workflow around it.
This page is intentionally category-based, because some repositories are public, some are private, and some are better shown in context. The main technical lanes I can present or build around include:
If you want a repository walkthrough, architecture explanation, or a hiring-focused technical selection, I can present the most relevant code samples by context: growth tooling, internal software, automation utilities, or multi-platform builds.