3.By and large, “knowing how” matters more than “knowing what”

For example, if you’re building a house I dare you to replace the architects with carpenters.

Furthermore software engineering is in such a sorry state (imagine if bridges were the physical equivalent of Word) because “know what” issues have been until fairly recently left entirely to the “know how” engineers.

If you know what to do, you can usually find out how to accomplish it. But if all you know is how you end up with early Microsoft products.

If software has taught us anything, its that “know how” and “know what” are very very different issues that require very different skills and temperaments to handle successfully, and that conflating the two is almost always disastrous for the end user.