I build at the boundary where chips and code have to agree — and chase bugs down the stack until the real cause shows up.
Computer engineering student at VCU, graduating December 2026. I work on FPGAs, embedded boards, firmware, and the testbenches that prove they work. I like building things you can see working: live demos, simulations, and tools I use myself.
Open to relocatingB.S. Computer Engineering · Dec 2026U.S. citizen
Live demos and recordings. The simulations use stated, made-up numbers, not any vendor's hardware or data.
Live demo · C++ firmware
Rack Fault Lab
A C++ BMC firmware core that keeps a GPU rack alive when hardware misbehaves — radiation bit-flips, silent data corruption, a GPU falling off the PCIe bus, coolant and power faults. Every fault is a HIL-style regression test with a pass/fail answer; one scenario runs with the policy off and fails on purpose, so you can see what the firmware buys.
A guided audio-and-diagram tour of the firmware above: the 10 Hz BMC loop, the per-GPU state machine, how it catches radiation errors and silent corruption, how it shares the power budget, and how the tests prove it. Thirteen chapters, ending in a ten-question self-quiz. Best with sound on.
The big-picture tour of my FPGA project: I programmed a Xilinx Artix-7 to present itself as a real PCIe device, so a computer discovers it, loads a driver, and talks to it. “I built a PCIe device on an FPGA, made it enumerate and respond correctly, and verified it with a test.” This is the hardware/software boundary I want to work on.
A reinforcement-learning agent flying a Crazyflie quadrotor through a procedural city, limited to what a real drone can actually sense — 32 distance rays and a small local coverage map. Simulation, learned autonomy and honest replays.
An on-stream character that moves with my real keyboard and mouse as I play, built on a passive Windows Raw Input reader in C, a local Python WebSocket hub and a browser overlay shared by OBS and an Electron window.