X Screenshots: Product Videos And Taste
Status: deepened milieu note
Source
- Date captured: 2026-06-18
- Source type:
screenshots - Platform: X
- Local source files:
external_material/archive/processed/Screenshot 2026-06-18 at 9.48.00 PM.pngexternal_material/archive/processed/Screenshot 2026-06-18 at 9.52.22 PM.png
Note: local filenames include a narrow no-break space before PM on disk. The
paths above are normalized for readability.
People / Organizations
- Wise / @trikcode
- Garry Tan / @garrytan
- Gideon Shalwick / referenced post
Neutral Summary
The first screenshot captures a post by Wise:
Tech has entered its funniest era.
You can spend 3 months building a product
just to discover the real job
is making short videos about the product.
The second screenshot captures Garry Tan endorsing a post about vibe coding not fully replacing thinking:
This is 100% right. If you know your market, your customer, and what problem
you're solving, you have taste, you know what is good and what sucks.
You can now fly.
Together, the screenshots point at two related claims:
- building is no longer the only hard part;
- knowing the market, customer, problem, and taste is now what lets a builder move fast.
Why This Caught Attention
These screenshots are compact social proof for the same broad pattern emerging across the batch: agentic building increases the relative value of audience, distribution, taste, problem selection, and content.
How Theme Theory Relates
The Wise post is a compressed version of the distribution problem: after you build, you discover that attention and communication are still required.
The Garry Tan post adds the judgment side: AI/vibe coding gives leverage to the person who already understands the market, customer, and problem.
Theme Theory can connect those:
The builder who knows the audience's object of interest has better taste about
what to build and what creative to make about it.
That is a useful formulation. The same understanding that improves product judgment also improves content judgment. The product and the short videos are not separate problems if both are organized around the same audience-side object.
Deep Corpus Comparison
These screenshots are small but high-signal because they compress the WTB/media intersection into two social posts.
The Wise post captures the builder surprise:
I built the thing, but now I have to make people care.
The Garry Tan post captures the judgment condition:
AI leverage works best when the builder knows the customer, market, problem,
and quality bar.
Theme Theory connects them through the object of interest. The same object should discipline both product and creative:
- what the product supports;
- what the videos explain or dramatize;
- what the customer recognizes;
- what the builder uses to judge good versus bad output.
This makes product videos more than promotion. They can be theme-satisfying artifacts: demonstrations that help the audience understand the problem, desired state, and support surface.
The note is also a useful reminder not to turn make short videos into a
shallow rule. The deeper rule is to make the object visible and credible.
Core Links
Candidate Concepts / Edges
- product build -> not enough without audience communication
- short videos -> creative support for product discovery
- market/customer/problem knowledge -> taste
- taste -> ability to judge product and creative against the object of interest
- vibe coding leverage -> strongest for builders with domain/customer judgment
Promotion Judgment
- Promote to core?
maybe - Reason: useful small examples for the "building is easier; taste/audience are scarcer" point. Probably better as supporting references than core anchors.
Open Questions
- Is taste partly the ability to recognize whether something satisfies the audience's object of interest?
- Should product creative be treated as a support surface, not just promotion?
- How do we keep "make short videos" from becoming the shallow takeaway?