Start with context, listen carefully, and diagnose before reaching for a familiar answer.
BUILDER // STUDENT // LEADER // PERSONCONNECT ↗
Build what
holds up.
My experience includes software development, IT support, endpoint management, home infrastructure, and automation. I enjoy work that requires both technical problem-solving and clear communication.
EXPLORE THE WORK ↓$ approach --scope
listen → diagnose → build → explain
$ craft --mode
development + systems + automation
$ direction
larger problems // useful outcomes_
Technical work is human work.
A solution can be technically correct and still be difficult to maintain, explain, or use. I try to account for the people who will rely on it after the immediate problem is solved.
I have learned that through software products, help desk support, endpoint administration, home infrastructure, and automation. In each setting, I need to understand the surrounding system and document the work clearly enough that someone else can follow it.
Take responsibility for the full experience—not only the technical step that happens to be mine.
Good technical work includes clear communication, useful documentation, and respect for the person affected.
A solved issue can become a better process, a reusable tool, or a system that prevents the same friction.
Learning through ownership.
diad // home infrastructure
A self-hosted lab built to connect storage, media, networking, containers, automation, and secure remote access.
Designed around Unraid and Docker, diad is where I test infrastructure decisions against real constraints: mixed storage, network access, service reliability, security, and a household that expects everything to simply work.
independent software platform
Software built as a teenager that grew into a product used by more than 100,000 people, including paid subscribers.
The project taught me far more than syntax. I had to turn feedback into product decisions, support users at scale, maintain stability, and take responsibility for an experience people depended on.
Windows endpoint modernization
Supported a company-wide endpoint modernization effort across a varied Windows environment.
The work required testing, deployment coordination, clear documentation, careful exception handling, and persistence. More than the final count, it demonstrated how dependable technical work is built from preparation and follow-through.
operations automation
Reduced repetitive communication and process friction through practical automation.
I look for the small repeated tasks that quietly consume attention. Turning them into consistent, reusable workflows creates room for deeper work and makes the process easier for the next person to understand.
A scope that kept expanding.
Curiosity became craft
Games led to command blocks, Scratch, C#, and the realization that I did not only want to use technology—I wanted to understand and build it.
Building for real users
Starting a software business as a teenager taught me product ownership, support, iteration, and the responsibility that comes when people depend on what you make.
Technology in the real world
Professional IT work broadened my view from code alone to users, endpoints, access, documentation, infrastructure, and the systems surrounding every application.
Development + systems
I am growing toward work that connects software, infrastructure, automation, security, and thoughtful problem solving rather than forcing those interests into separate boxes.
Different layers, one perspective.
These skills overlap in everyday work. Development helps me automate repetitive tasks, systems knowledge helps me understand where software runs, and support experience keeps me aware of the people using it.
DEVELOPMENT
01JavaScript
02C#
03Python
04Java
05Algorithms
06Data structures
SYSTEMS
01Windows
02macOS
03Linux
04Docker
05Unraid
06Networking
OPERATIONS
01Active Directory
02Endpoint management
03Patching
04Automation
05Documentation