[SeasonalEnnui]

Same. I’ve adopted the “write it twice” (a play on WET/DRY) methodology to software & electronics development. Write v0 (formally called a “proof of concept” I suppose but perhaps a bit more developed), or protoboard a circuit, learn the problem domain, throw it out and write v1, or layout the PCB. That’s my compensation for being unable to visualise.