Make it usable
Good software should remove friction, make the next step obvious, and respect the person using it.
Personal site v1.2 / playable demos live
Computer science student at the University of Louisville building useful software, cleaner data workflows, and web experiences with a little motion in the room.
I am a computer science student at UofL's J.B. Speed School of Engineering, open to software engineering, data analytics, and technical internship roles. The thread through the work is practical: make the messy thing easier to track, explain, automate, or use.
That has shown up in store inventory tools, retail analytics notebooks, front-end weather visualization, livestream production, student org work, and the everyday operations problems that reward clear thinking.
A mix of analytics, automation, games, and systems coursework. The game projects now open as browser demos, so the portfolio does more than point at code.
Cleaned 9,994 retail orders, explored discount-profit behavior, and compared baseline ML models with a decision tree reaching 94.36% accuracy.
GitHubSanitized Electron workflow for batch IMEI lookups and Google Sheets inventory updates, rebuilt around environment-based configuration.
Play nowA browser-playable take on the 3x3x3 game, with layered boards, full spatial win detection, and a clean two-player flow.
Play nowA polished web board based on the Pygame project, with legal-move highlights, captures, multi-jumps, kings, undo, and reset.
GitHubSystems project using forked mappers, bounded buffers, sender threads, System V message queues, and reducer aggregation.
GitHubStorage benchmark that creates block files, samples randomized reads, and reports median latency for repeatable low-level I/O tests.
Good software should remove friction, make the next step obvious, and respect the person using it.
Get the thing working, learn from it, then keep tightening the details until it feels inevitable.
Data, operations, community work, and web design all meet when information needs to move clearly.
Add richer case-study pages for the strongest repos as the screenshots, metrics, and demos mature.
Keep tightening the GitHub READMEs so each project explains the problem, setup, and result quickly.
Keep tuning the site as the resume evolves through internships, classes, and shipped work.