pull down to refresh
Publishing this roadmap is what surprises me. I don't care much how they get to the stated goal, but I would think the goal of a roadmap on a website like this is to inform your users of your plans. There doesn't seem to be much information here.
reply
Hmm I think in this case the goal of the roadmap is a search for validation (or recognition, lol, but let's stick with the sunny case.) This can be done but why would anyone want to read it? No one is going to invest in something that can be coded on a $20 plan either. Let's just hope someone reads it and asks some "why" for free and then everyone can move on.
reply
I have such roadmaps too, though a lot larger. They're responses to "plan this 20 pager of specs into work packages" prompts. Then per work package I trigger "plan this in detail", which I then review and edit. And when satisfied I send the whole package over: "execute this". And then I have massive review pressure until I am mm away from burn out at 5am in the morning. Then I take a day off and carry on. It's easy. Anyone can do this. If you want to. And know when to stop. And have an idea about how to do development.
The big difference though: I don't publish Claude's code.