The weird thing is that I haven't really seen many people direct wire the halves together. It's really only UART, I2C, or an IO expander. It's only really viable for a 40-45% keyboard, but so far it's working great. I haven't had interference issues so far.
October 4, 2025 at 8:06 AM
The weird thing is that I haven't really seen many people direct wire the halves together. It's really only UART, I2C, or an IO expander. It's only really viable for a 40-45% keyboard, but so far it's working great. I haven't had interference issues so far.
I've been experimenting with tenting, but I'm not sure if I'm all in. For long extended typing I think I prefer flat, but for regular coding work where it's not constant, the tenting feels really good
October 4, 2025 at 7:45 AM
I've been experimenting with tenting, but I'm not sure if I'm all in. For long extended typing I think I prefer flat, but for regular coding work where it's not constant, the tenting feels really good
I also wrote my own firmware because I'm insane apparently. It's got everything I would have used in QMK: layers, tap-hold, combos, macros, WS2812 control for the status LEDs. I didn't even use the tinyusb stack that comes with the pico SDK, so I got some practice debugging low level USB issues 😅
October 4, 2025 at 7:41 AM
I also wrote my own firmware because I'm insane apparently. It's got everything I would have used in QMK: layers, tap-hold, combos, macros, WS2812 control for the status LEDs. I didn't even use the tinyusb stack that comes with the pico SDK, so I got some practice debugging low level USB issues 😅
Totally. The thing is, i still have a day job where I make production stuff. That takes a whole different kind of thinking and approach, and you're rarely down in the nuts and bolts (even when it's firmware!)
January 22, 2025 at 6:55 PM
Totally. The thing is, i still have a day job where I make production stuff. That takes a whole different kind of thinking and approach, and you're rarely down in the nuts and bolts (even when it's firmware!)