[0] "The Humble Programmer" - http://www.cs.utexas.edu/~EWD/transcriptions/EWD03xx/EWD340....
[0] "The Humble Programmer" - http://www.cs.utexas.edu/~EWD/transcriptions/EWD03xx/EWD340....
I still think it's helpful from time to time to think a bit deeper about the details of what's actually happening below the top couple layers of abstraction, though :)
You know what debugging is? It's patching up the leaks in abstractions. Thus, we all think about what's behind the abstraction pretty much every working day.
Ya'll soap-boxing is annoying the fuck out of me.
I suggest you not take all of this so personally.
Have you read the lecture that okal posted the link to? It's from the early 1970's and speaks to the early days of when abstractions were first being implemented for computers in general. Perhaps it is you who does not understand what abstraction means.
Me? I write in machine code – in 'raw, unadorned, inscrutable hexadecimal numbers. Directly.
Or, you know, being able to effectively troubleshoot when something breaks or when abstractions leak.