> But here's the part you didn't get. If you are going to be a programmer, you should think like an engineer. You need to understand your machine and your code

> But here's the part you didn't get. If you are going to be a programmer, you should think like an engineer. You need to understand your machine and your code and the effects of it all. Totally. And my website aims to help people understand this aspect of their machine better, and it does this quite well (other people's observation, not just my assertion). > I believe your hypothetical audience doesn't exist. Give them some credit. There's simply no reason a competent software engineer cannot understand Goldberg. That they can understand it doesn't mean they have to invest the hours it would take to go through all of it with rusty formal math skills, when their immediate problem or question concerns ony a small (and not immediately discernible) part of it.