Make the state visible.
Good interfaces and good operations both help people understand what is happening, what changed, and what to do next.
About · Engineer in progress
Curious about
the whole system.
I’m Charlie, a fourth-year Computer Science Engineering student at Michigan State University.
I care about software that is useful on an ordinary Tuesday—not just impressive in a launch video.
The throughline
From an interface
to an operating reality.
My best learning happens when a system has real users, real data, and a reason to stay healthy. That has pulled me beyond isolated features into access control, synchronization, deployment, observability, and recovery.
The projects here span store operations, personal software, and private infrastructure. They look different on the surface, but each is an exercise in turning ambiguity into a system someone can understand and depend on.
Education
Michigan State University.
Education at Michigan State University
B.S. Computer Science Engineering
Fourth-year student · East Lansing, Michigan
Coursework provides the theory; building and operating systems supplies the feedback loop. I’m especially interested in the boundary between application engineering and the infrastructure that makes an application trustworthy.
Working style
Direct, deliberate, iterative.
How Charlie works
Prefer explicit boundaries.
Clear ownership, typed contracts, and narrow permissions make systems easier to change and harder to misuse.
Learn from production.
Real use exposes the difference between a clever implementation and a durable product. I want that feedback early.
Current interests
Problems I keep returning to.
Useful abstractions, local ownership of data, calm operational surfaces, and systems that can explain their own health.
Say hello