Construction was never the best metaphor for programming. The compiler constructs the code. Software dev is closer to building architecture than construction.
This is probably the best way to read it: Do not presume to correct another person while remaining blind to your own faults. Examine and correct yourself first; only then are you in a position to help your brother with his.
It literally is meant as a beam, a bit of exaggeration for emphasis.
So we are meant to assess and help others but first must correct our own selves.
The one I get constantly is we want "custom reporting". Well what the hell is that really? Why, why, why do you need that? Then I just build a new feature they will actually use and defer "custom reporting" for another month.
At our small company we are hooked on individual subs. But yeah a larger dev shop can't really pull that off and I get how they'd be dying by the token cost.
I don't understand why we tolerate this. We'd never hire someone that interviewed with this communication style and if we did we'd probably pip them fast.