Yes, it's the thing with keyboard preferences - they are highly subjective. They can depend on what OS you use, IDE/editor, shell, even your least hated browser.
For example, I don't care for the Step in/Step out keys because I don't use debuggers much and even if I did I probably wouldn't need a special key for those tasks - I would've just mapped them to a chord that I use without looking at the keyboard - or something like that.
I think the "ideal programmer's keyboard" should cover the tactile front (key-press depth and feel, size and arrangement of the keys) and allow as much customization as to mappings as practically possible - perhaps going as far as providing several sets of stickers on a sheet and letting the user attach them to the keys.
It should be noted that the maker of that keyboard (WASD Keyboards) sells customizable keycaps for their other keyboards. It seems reasonable that if the CODE keyboard sells well they'll probably offer to sell customizable keycaps for it as well, so you wouldn't even need stickers, just order a handful of custom keycaps and swap them out yourself.
For example, I don't care for the Step in/Step out keys because I don't use debuggers much and even if I did I probably wouldn't need a special key for those tasks - I would've just mapped them to a chord that I use without looking at the keyboard - or something like that.
I think the "ideal programmer's keyboard" should cover the tactile front (key-press depth and feel, size and arrangement of the keys) and allow as much customization as to mappings as practically possible - perhaps going as far as providing several sets of stickers on a sheet and letting the user attach them to the keys.