Take a look at the Das Keyboard 4 Professional Mechanical Keyboard[^] . I've been using one of these for about 5 years now and it's worth every penny. The two port USB 3.0 hub is a plus (I use it constantly), but would stick with this keyboard even without it. It's sturdy, all Cherry-MX. It's not a programmable but for work (non-gaming) I use AutoHotkey (and a misused StreamDeck).

Ken - I build things that allow others to build their things.

I come at this issue from an SCM viewpoint and while I think there are valid arguments to both separation and collapse, I tend to see many development efforts where the separation was based on how easy Visual Studio makes it. If the developers have discipline, this isn't necessarily a bad thing, but if not, you can quickly get spaghetti code. I personally believe that all other things being equal, fewer artifacts is better. There are circumstances where they should split, but I default to not creating an extra assembly. I'd recommend reading the 'White Book' Partitioning code base through .NET assemblies and Visual Studio projects found here: NDepend White Books[^] K.