[decompiled_dev]

I think design patterns should be more descriptive, but people try to use them prescriptively.

Being able to say "circuit breaker" pattern or "visitor" is a time efficient way to communicate complicated ideas. Its value is being able to conserve the limited bandwidth speaking has.

Bad coders will always find something or another to justify their work with and it just so happens the most popular book is often referenced, for good and bad.

[reval]

Both of you nailed it. I’ve always used the term “implied implementation” to describe the phenomenon where a description becomes prescription.

[vacuity]

You're right, but the key thing about description and prescription is that they aren't really separate. You constantly have to ask "does this work well here?", "should I replicate it there?", and so on. They deal with the same thing in different modes of interaction, and so being able to structure these analyses is important to doing each well.

[zdragnar]

You'd be surprised at how often seniors don't actually ask those questions when it comes to prescriptive standards. They get used first and questions only come up when it's too late.