back

by sixhobbits·7mo ago·view on hn ↗
This is an interesting opinion but I would like to see some proof or at least more details.

What plans are you using, what did you build, what was the output from both on similar inputs, what's an example of a prompt that took you two hours to write, what was the output, etc?

1 comments
Heya, author here!

I'll try to answer these one by one, but I will just note that a lot of my prompts are domain specific so it's hard to share those.

- I don't use any plans — my writing is the plan. The Plan Mode in Claude Code is excellent, but as I've switched to Codex (which doesn't have one) I will simply write up a nice long prompt and then add "Please ask any clarifying questions you may have, or for any additional details that you need" — and it works great! I may go back and forth for anywhere from 5-30 minutes depending on what else is needed, but that's basically the experience of using Plan Mode in Claude Code too.

- I've built quite a few recent features for my app Plinky [^1]. I've made a few meaningful contributions to my open source project Boutique [^2] (and have been having AI asynchronously sketch out a large new database relationships feature). I built my new blog and my workshops pages [^3] with Codex as well. Truth is I do practically everything in Codex and Claude Code these days, so I'd have more trouble listing what I haven't built lately.

- Plinky's upcoming Reader Mode is a good example of a prompt that took me two hours, but the feature isn't yet in the app so I'd prefer not to share the prompt. But I can share the first draft of the prompt for Boutique's relationships feature sine that's open source. [^4] I've been experimenting with using ChatGPT Pulse to make progress on it every day (simply by asking it to!), and much to my surprise it's been designing a new API day by day in a way that's far from perfect but certaintly has been very interesting.

The honest truth is that this one did not take two hours and I wrote it on the bus so it's probably not perfect, but the descriptive process is effectively the same. For a feature like Reader Mode you would have to capture more details to scale up to the additional complexity of a domain-specific feature with client and server components, a new download queueing pipeline, amongst other abstractions.

Hope that answers your questions!

[^1]: https://plinky.app [^2]: https://github.com/mergesort/Boutique [^3]: https://build.ms [^4]: https://gist.github.com/mergesort/04a77c47ea4cb6433aa9ade4e1...

Thanks! Would be interesting to compare with a looser approach, I use shorter prompts that take me a few seconds to write and it's also built some impressive stuff for me, I've mainly been using claude code and a bit of Gemini/Amp/Droid so I'll add Codex to the mix this week. So far I don't really feel the difference much between tool or model.