Right now we're focusing on reference docs and soon the app will be able to write full documentation content.
We want to focus on incremental changes to docs (one PR at a time) so the content is easy to verify and merge.
Right now we're focusing on reference docs and soon the app will be able to write full documentation content.
We want to focus on incremental changes to docs (one PR at a time) so the content is easy to verify and merge.
This is a solo startup that I've been working on for 2 years now. It's a labor of love and I'm very lucky and thankful that it's big enough to surprisingly pay all of our bills. Still constantly feeling FOMO over all of my startup buddies working with AI and LLMs while I plug away at old maps and GIS .
It gets ~80K MAUs and just slowly and consistently is growing organically through word of mouth through history focused communities. I'm currently playing with expanding the coverage internationally as I still only support the US which is a wickedly fun project.
How are people using auto-edits and these kind of higher-level abstraction?
So for an API call that costs $0.50, the end user is charged $1; and from that AI API earns $0.50, the webapp creator earns $0.40 and the host earns $0.10.
I'm trying this out with https://codeplusequalsai.com right now but it's not clear to me yet that it will take off!
But clearly, the value to you should be that you could earn $ based on the token usage from end-users.
What's your target audience? developers?
I am struck by how much these kinds of context documents resemble normal developer documentation, but actually useful and task-oriented. What was the barrier to creating these documents before?
Three theories on why this is so different:
1) The feedback loop was too long. If you wrote some docs, you might never learn if they were any good. If you did, it might be years later. And if you changed them, doing an A/B test was impractical. Now, you can write up a context markdown, ask Claude to do something, and iterate in minutes.
2) The tools can help build them. Building good docs was always hard. Especially if you take the time to include examples, urls, etc. that make the documentation truly useful. These tools reduce this cost.
3) Many programmers are egotists. Documentation that helps other people doesn't generate internal motivation. But documentation that allows you to better harness a computer minion to your will is attractive.
Any other theories?