That sounds fun, I designed the instruction set on my CPU myself and I didn't get around writing a compiler for it (I only wrote an assembler).
Since I designed the instruction set I made some very quirky design decisions to make the test programs I was writing easier, instructions were 16bit but only 6 bits were used for the instruction so I had a lot of single-word instructions that did a lot of heavy lifting for my programs.
Did you really do that at the bachelor level? I feel like my uni was a bit abnormal on how many hardware classes and projects we had at a bachelor level for computer science.
That's "full stack" development :)
Also wrote a BBC Micro emulator, which was great fun.