For me, each layer of abstraction should roughly correspond to people's roles.
In my line of work (finance) it's a little more complicated than what the article states.
There are people who specialize in deep computational optimization.
There are people who do micro financial models
There are people who do macro financial models
There are people who do user interfaces
There are people who do the piping between all these
The ideal to aim for is that each layer of abstraction is cut around those fairly well defined roles. Each person should be able to own their piece of the codebase and hopefully manipulate objects/languages of the right level for them.
In the dishwasher example, the middle layer should be cut in the "electronics layer" and the "hydrolics layer", the electronics layer interfaces with both the user and the hydrolics layer, but the hydrolics layer never interfaces with the user. And it's easy to see that the electronics and the hydrolics are not designed by the same person.
It's a way of framing things that makes sense for me.