| Sadly the vast majority of developers might know that there is a tool called debugger and might also know how to set a breakpoint.
But that’s where it stops.
No drive to see what your debugger offers you.
callstack? what’s that?
Conditional Breakpoints? Huh? I hope that instead of aiming further down the abstraction layers, they instead aim up and try to get the hang of macro level stuff, metaprogramming, abstractions which I most often put off as "that’s just a fad" If something like containerization or container orchestration sticks around for 5 or 10 years I'll maybe take a proper look at it. Until then it is ‚just a trend‘ and takes mental space I feel spent better digging down. Because that’s where software is interacting with hardware (the real world).
That’s the abstraction layer where you can 'actually move the world', where goods are created. Not everybody is capable or experienced enough to move across different abstraction layers and have a proper mental models for each. SOMEWHERE you will probably have to draw a line. Some people draw the line at 'writing software'.
Execution target (understanding the hardware / runtime) are out of focus for effectively all programmers.
I think partly because languages, tutorials, bootcamps don't bother to dig deep there because 'the compiler will take care'. It just is not teached that way. What do you mean with Solaris? Sun? PDP? It is just a computer. Java is cross platform. How it does that? Thats the JVMs job, not my job. I just write the software. |