a single source, nothing corroborates it
Post the problem and let the audience debug it
Put the thing you are stuck on in front of the people following the work, and ask for critique while it is still in progress rather than after publishing. Builders report getting expert help for free this way, including a diagnosis of a bug they could not find, because the audience a public build attracts contains people who have solved it already.
The method
- 01
Building in public buys you free expert help. Kahl posted a memory leak he could not diagnose to Twitter and the developers following his journey gave him the feedback that found it.
- 02
Solicit critique from a private community and from your followers while the thing is still in progress, not after publishing.
What it returned
Days of solo debugging and a new larger server failed. A Twitter post to his developer following surfaced the cause.
Justin took draft intros and candidate thumbnails to the MegaMaker Slack, the Transistor team Slack and Twitter, and the outside suggestions improved both.
Sources
- What makes you click on a YouTube video?Justin Jackson · justinjackson.ca · Optimizing the first five seconds · undated
- Doing Things that Don’t Scale …Unintentionally – The Bootstrapped FounderArvid Kahl · thebootstrappedfounder.com · 2024-07-26
the second source
Three plays a week, for the phase you are in
No roundup of links, no news. Three tactics more than one builder arrived at separately, with the numbers each one returned and the disagreements left in.
More in social
- Concentrate on one platform until it works11 unconnected · contested
- Gather the audience before there is a product6 unconnected · contested
- Fire the launch into the audience you already have6 unconnected · contested
- Post the numbers, not the commentary5 unconnected · contested
- Republish the winners with a new hook5 unconnected
- Cut one long piece into weeks of social posts5 unconnected