I definitely recognize myself in this. I consider myself a decent programmer but I also know quite a bit about electronics and even a bit of Verilog/VHDL. Not e

I definitely recognize myself in this. I consider myself a decent programmer but I also know quite a bit about electronics and even a bit of Verilog/VHDL. Not enough to work as an ASIC/FPGA engineer, but enough to understand the broad concepts and how it all fits together. If you talk to me about timing violations and setup times and clock trees I'm not completely out of my depth. All that happened pretty much by accident, mainly because I was always interested in all things low level, but it proves really advantageous in my career. Basically if a problem stands at the interface between hardware and software I tend to be massively more productive than a very good software engineer who knows very little of electronics or vice versa. If we have a problem like "we have this driver that seems to lock up because it misses an IRQ, but we're not sure if it's a software race or a hardware problem" I can usually help. Of course that's all fairly niche, but as long as the niche is big enough that's not an issue. It's all about finding complementary skills. There might be a need somewhere for a good software dev that also very good at Sumo, but that's probably not very common...