> The book _is already the important information_. This is evident that not reading it casued problems.

I agree. The problem is that it's too much upfront information.

> Then imagine getting upset because the bolts don't work as you thought they did.

I'm more imagining that the engineer glances at the documentation and rejects the complicated bolts unless there is a really really good reason to prefer them.

Programmers, on most projects, are backed into a corner of horrific complexity. The proper comparison to engineering is refusing to do the project entirely. An engineer wouldn't be reading all these details either. So you shouldn't be using that as your factor to compare professions. It's not just "Would they read everything? Yes/No" when there's orders of magnitude difference in the amount to read.

And your average webpage isn't so important you have to refuse on ethical grounds.