design-patterns - 为什么 'smoke and mirrors' 是一种反模式？

Question

我最近正在阅读 Wikpedia's list of Anti-Patterns 并注意到这包括在内:

Smoke and mirrors: Demonstrating how unimplemented functions will appear

为什么这是一件坏事？我唯一能看到的是，如果你从来没有真正开始实现上述功能。如果功能在正式规范中，“保证”完成怎么办？为了向潜在客户展示他们的能力，这样做是否仍然很糟糕？

Answer 1

要了解为什么烟雾和镜子会成为反模式，请查看 Smoke and Mirrors 维基百科条目。从文章:

Smoke and mirrors is a metaphor for a deceptive, fraudulent or insubstantial explanation or description. The source of the name is based on magicians' illusions, where magicians make objects appear or disappear by extending or retracting mirrors amid a confusing burst of smoke. The expression may have a connotation of virtuosity or cleverness in carrying out such a deception.

In the field of computer programming, it is used to describe a program or functionality that does not yet exist, but appears as though it does (cf. vaporware). This is often done to demonstrate what a resulting project will function/look like after the code is complete — at a trade show, for example.

More generally, "smoke and mirrors" may refer to any sort of presentation by which the audience is intended to be deceived, such as an attempt to fool a prospective client into thinking that one has capabilities necessary to deliver a product in question.

很多时候，为了获得/保持资金，烟雾和镜子被用来通过演示给管理层或客户留下深刻印象，但下面没有真正的代码。这在一段时间内有效，但最终会导致其他反模式(意大利面条代码、blob 等)，以便在实际要求时尝试获得真实的东西。

以 Smoke and Mirrors 开始的项目往往以可怕的方式结束。就像一段关系一样，如果你用谎言来开发你的代码，最后一切都会分崩离析。