All software should be a tool or language because it reduces your risk of failure.
I’m certainly not the first one to think of things this way. There is an entire area based on the idea of Domain Specific Languages. The idea is to create a language around the problem you’re trying to solve in order to make it easier to solve the problem.
I'm glad I read this, because it's absolutely and completely wrong.
The point of using domain-specific language (note the lack of caps) is to reduce the distance between what you're building and what your customer wants you to build.
I suppose if you want to attack something other than the fundamental assumption in the paragraph I quoted, you might go for the satire:
The idea is to create small, loosely-coupled units of behavior around the problem you're trying to solve in order to make it easier to solve the problem.
No one's getting rich or famous talking about encapsulation and nomenclature, though.