🚀 How do you prepare to ship faster?
by•
Product Hunt’s Ship Faster Day is coming on September 30th!
The idea is pretty fun: launch something, get feedback, and then build and ship the requested improvements as fast as you can.
With only two days left, I started wondering:
How do you prepare yourself for a day like this?
Do you rely on your ability to make fast decisions and move quickly?
Or have you built an ecosystem around you - tools, workflows, processes, AI, whatever - that helps you implement things faster?
And how do you actually increase your speed as a maker?
Would love to hear your tricks before the big day =)
173 views
Replies
i try to keep things simple when I need to ship fast. fewer things to decide means less time wasted.
@anne_charlotte_mornington_ But what if you get a feature request you have to ship today and you can’t keep it as simple as you’d love to =)
What helps you ship faster when you have very little time before lounching
@shivam_kushwaha16Â Critical thinking =)
@adana yeah definitely having a simple process before launch makes a big difference especially when time is tight
We ship with our voice. With tools like @Wispr Flow and we’re actually building 25–35% faster. No more typing.
Also workflow:
> Opus 5.5 is for design work
> Astra is for planning work
> GPT Sol Extra High is for execution
> Astra is for reviewing the work
@byalexai Great! I have Wispr installed on my pc as well. Haven’t worked with it recently, so thanks for the reminder =)
And thanks for sharing your tool stack as well!
I'm going to remove my code reviewer so i can only just create new features... my best idea =P
@ben_reichwein Haha =D Good one !
How do you prepare yourself for a day like this?
- 100x push-ups/day
- 100x chin-ups/day
- Carb-loading sushi 😅
@ruzgarzere Haha, that’s a real speed-up list for fast shipping =D
I run about a dozen Claude Code sessions at once, one per project, so a lot of the speed comes from that. For a client team I consult for, requests usually get shipped the same day. And I stopped reading every line a while ago, E2E tests are what catch things now.
@hisashispace Thanks for sharing your experience! It’d be nice if you did a launch today =) It would be interesting to watch you ship so fast.
A dozen parallel sessions changes the review problem. I’d give each client run one E2E command and refuse the handoff if it never ran. I built MartinLoop. It is open source. If you want, I’ll help govern one client run and you can tell me where it gets in your way.
The idea of combining tools, workflows, and AI to reduce small delays really stands out.
@marissa__bronfman do you have some upcoming launch?
Fast shipping starts with deciding what done means before the agent starts.
I run a preflight before spending the full run.
```bash
npx -y martin-loop@latest preflight "ship the requested improvement" --verify "npm test" --accept "requested feature works" --accept "existing behavior remains intact" --allow-path "src/**" --allow-path "tests/**" --budget-usd 3 --max-iterations 2
```
If it clears, switch `preflight` to `run`.
I built MartinLoop because faster agent loops are useless if the handoff still takes hours to review. It’s open source if you want to try it.
@keesan12Â wow ! of course, can you share some link?
@adana Yep. Start here
https://github.com/Keesan12/martin-loop
Fastest first run
npx -y martin-loop@latest start
Send me what you are shipping and I’ll help you set the first acceptance check.
@keesan12Â Thanks for sharing... I'll check it with our tech teammates =) and ping you
@adana Thanks Adana. If your team tries it, send me the repo stack and the check you use to call a change done. I’ll help you shape a small first run. Even a rough bug report would be useful.