Having marketed to developers in the past I found that: 1) Producing quality content and examples showcasing the product's use/solv...
Having marketed to developers in the past I found that: 1) Producing quality content and examples showcasing the product's use/solving a problem are helpful. In writing that content you'll learn more about your market and what matters to them. Blogging was invaluable in helping me understand what developers needed, what they didnt, and what they responded to. 2) Clear documentation explaining how the product works. It shows that you care about your development and helps devs understand exactly how it works (which they will care about). 3) Communicate how you are either removing a pain point or removing work from their day. Most new tools are all about conveniently do X task.
Posted by cblock811 on May 20, 2015, 6:58 PM
Tags
Related issues
- The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments
hackernews (Other)
The biggest problem with having an LLM do this, from what I've observed of at least frontier models, is that the way they are trained...
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
Having marketed to developers in the past I found that: 1) Producing quality content and examples showcasing the product's use/solv...
Having marketed to developers in the past I found that: 1) Producing quality content and examples showcasing the product's use/solving a problem are helpful. In writing that content you'll learn more about your market and what matters to them. Blogging was invaluable in helping me understand what developers needed, what they didnt, and what they responded to. 2) Clear documentation explaining how the product works. It shows that you care about your development and helps devs understand exactly how it works (which they will care about). 3) Communicate how you are either removing a pain point or removing work from their day. Most new tools are all about conveniently do X task.
Comments (0)
No comments yet. Start the discussion.