I'm a computer engineering student who's drawn to the layer where hardware physically turns into software, where a voltage on a wire becomes a bit, a bit becomes an instruction, and an instruction becomes something you can see, hear, or measure.

That thread runs through most of what ends up in this profile: designing digital logic in VHDL, writing embedded C close to the metal, and occasionally going all the way down to hand-assembling a binary file format byte by byte just to know exactly what a "player" is doing when it hits play. I've built a 16-bit CPU up from a single NAND gate, written the assembly that runs on it, and traced audio samples all the way from a sine function to the raw bytes on disk. I'd rather understand a system completely than trust an abstraction to hide it from me, which also explains why I run and maintain my own self-hosted infrastructure instead of renting someone else's.

I'm oriented towards the aerospace and real-time embedded systems industry. I treat chips and the firmware as one design problem instead of two separate ones handed off in sequence, which is why I'm into the specific niche of SoC/Systems Architecture.

Hardware / Embedded

Systems / Infrastructure

Tools

Most of what's here follows the same method: start from a given first principle, a logic gate, a raw byte, a signal on a bus, and then build upward only after understanding exactly what each layer is buying you. A CPU built from a single NAND gate. A WAV file built one byte at a time instead of through a library call. A homelab built on bind-mounted directories and declarative compose files instead of opaque managed services. My goal is to earn abstractions before relying on them.

• Real-time operating systems and firmware for resource-constrained hardware
• Hardware-software co-design workflows, where the chip and the firmware are designed together
• Systems and network architecture like self-hosted infrastructure, zero-trust networking, Infrastructure as Code