Of course I don't expect to wax poetic about the finer technical details of an implementation- what I mean is he tends to get frustrated at the technical limita

Of course I don't expect to wax poetic about the finer technical details of an implementation- what I mean is he tends to get frustrated at the technical limitations, but has no interest in understanding those technical limitations so that he might curb his expectations and align them more with reality. Example: I wrote an ETL pipeline that processes "hundreds of millions" of records. It takes several hours to run (on my goddamn desktop computer). He doesn't understand why it takes "so long", and doesn't want to understand why. Also little interest/desire in paying for server compute that might get it done faster.