Earlier quoted context omitted.
I don't think that is a good analogy. The end product (app/house) is what the code actually does. What you use to make that product is a tool, including what language you use.
I agree. It's just like how a carpenter's best tools are English, arithmetic, and blueprints.
All those things do help, but a carpenter can do the same job with an axe, a saw, a chisel, a knife, or a froe but in the end what they are doing is cutting wood. If you're a programmer and you don't look at languages as a tool you are doing yourself a disservice. In the end you just need something to turn some data into a different kind of data, everything else is a tool to do that one thing.