EE, bottom-up problem solving; CS, top-down problem solving? EE's that I have worked with seem to understand system function deeply first, and build around it.

EE, bottom-up problem solving; CS, top-down problem solving? EE's that I have worked with seem to understand system function deeply first, and build around it. CS's usually mock-up simple versions, get it right, then optimize later. Broad generalization I know, but do others observe this? Possible reasons: 1) high cost of iteration in most hardware systems vs software. 2) University educational strategy in CS vs EE. 3) Availability of easy-to-use, quality, low-cost tools for software vs hardware.