Pretty much any time I cross domains with another engineer. I'm an embedded engineer in a team of highly advanced RF and FPGA engineers. Every time I'm given a task it ends up something like "this board has 6 active ICs and I'm spinning up an FPGA to read an encoder knob, can you find an LED driver?" And then I replace the entire circuit with a single microcontroller.
Conversely, my uninformed suggestions on their work often winds up being incredibly overcomplicated because I don't understand the domain as well.
That's one of the benefits of being in a well balanced team. We can collectively converge on ideal solutions where individually we couldn't.
Comments
Pretty much any time I cross domains with another engineer. I'm an embedded engineer in a team of highly advanced RF and FPGA engineers. Every time I'm given a task it ends up something like "this board has 6 active ICs and I'm spinning up an FPGA to read an encoder knob, can you find an LED driver?" And then I replace the entire circuit with a single microcontroller.
Conversely, my uninformed suggestions on their work often winds up being incredibly overcomplicated because I don't understand the domain as well.
That's one of the benefits of being in a well balanced team. We can collectively converge on ideal solutions where individually we couldn't.