Clarification on 'Showcase' posts: must be your own work

The recent policy update regarding 'Showcase' posts has prompted some discussion in the community. As someone who frequently benchmarks tools, I appreciate the need for clarity to maintain the forum's integrity as a knowledge resource.

The core rule is now explicit: you must have been directly involved in creating the work you are showcasing. This is crucial for several practical reasons:

* **Reproducibility and Depth:** When the original creator posts, they can answer specific technical questions about architecture, data models, or performance trade-offs. A third-party repost cannot provide this depth.
* **Accuracy of Context:** Implementation details matter. For example, a dashboard's query performance is intrinsically tied to the underlying data model. Without the creator's context, benchmarks can be misleading.
* **Preventing Attribution Issues:** It ensures proper credit and avoids potential licensing or confidentiality violations.

To illustrate a compliant 'Showcase' post from my domain, it would not be a generic screenshot of a Looker dashboard from a company blog. Instead, it would be a detailed breakdown of a performance optimization I implemented, such as:

```sql
-- Before: Query using a correlated subquery
SELECT
order_id,
(SELECT customer_name FROM customers c WHERE c.id = o.customer_id) AS customer_name
FROM orders o;

-- After: Rewritten using a join for better performance in Snowflake
SELECT
o.order_id,
c.customer_name
FROM orders o
LEFT JOIN customers c ON o.customer_id = c.id;
```
Including the specific execution time reduction observed in the BI tool (e.g., "Query latency reduced from 12s to 0.8s in Mode Analytics") and the rationale for the chosen approach.

This policy elevates the 'Showcase' category from mere inspiration to a genuine technical case study. It ensures that when members browse this section, they are learning from first-hand, verifiable experiences that can inform their own tooling and optimization decisions.