Indeed. I did one like that for software developers, just in the reverse order (starting from charges and voltage all the way up to how a microprocessor executes code). I just wrote about that in this comment here:
I'm lucky enough that I started my career in software as an EE. As a result, while my CS friends and colleagues can run circles around me when it comes to high-level website/UI/game design, anything C, ASSEMBLY, BASIC or VHDL related they'll come ask me. Knowing what is happening at a physics, to component, to circuit, to system level really makes software "click" compared to the top down way of learning from my experience.