Probably because they don't need to think about those things. I started my career as an Embedded Software Engineer, and memory allocation, and clock cycles han

Probably because they don't need to think about those things. I started my career as an Embedded Software Engineer, and memory allocation, and clock cycles hand to be managed. Our software ran on systems with limited memory, and had to fit in one 60hz cycle. We supported VAX system that used VAX Floating point, and had to be cognizant of both floating point conversions AND endian byte encoding. These days, such concepts are basically just trivia answers for interview questions. I had to think about those things because it was required. System software would crash, and debugging it on an expensive government flight sim 1000 miles away was impossible. Perhaps for the developers you work with, they don't need to think about those things because they're not required to. After all they have access to a dedicated DBA/SRE/DevOps/Architect guru.