Ask HN: What's the best way to get developers to try a new devtool?

Of the two options, I prefer to start here — https://livecycle.io/

I'll have a look at a tool if:

1. What is does blows my mind and/or it think it might change the world.

2. I'm super curious about how it works (the technology behind the tool).

3. I think that today or sometime in the next 12 months the tool will help me get shit done.

For example, not one hour ago I was blown away by the potential of WasmEdge (https://news.ycombinator.com/item?id=33792322). Already downloaded it and run its Hello World program.

Commodore 64 emulation under raspberry pi would allow for running off battery, make it poratable, and allow for using internet interface & modern storage devices.

All of which wouldn't change the groups understanding of how to use the old SDK.

With extra resources on pi, would be able to port everything over to open source version of VMS & use non-monochromatic terminals! (perhaps even emulate the c64 under openvms and slowly roll out port behind scenes)

Now, would just having a link to go see what can do with SDK been as interesting a read?

Perhaps your friends interviewed potential customers (i.e buyers not just users) and arrived at marketing it as a dev tool for dev teams...

In my opinion - I'm not so sure if the product should be marketed to "dev teams" per se! To me it looks like a collaboration tool around product development... not just for developers.

I would think the primary buyer would be PMs (Product / Project Managers) who would then push for the tool-use onto the dev teams as a way to improve collaboration and close the feedback-loop across all stakeholders (design, marketing etc). Yes, for that to be a success it requires devs to love it and indeed make thier job easier, but I don't think they're the primary buyers. Developers, in general, are notoriously hard to sell to because they filter out marketing jargon!

It has to be a lot better than what I'm using right now or give me a clear capability that nothing else has. There's that term, "There's no silver bullet" and that makes some people skeptical of the next best tool. It hurts if the learning curve is too long and good documentation/tutorials can help. Another consideration is if it comes out as a competitor to other tools in its class (e.g. UI Component libraries) during a version upgrade or when starting a new project, which is when I would evaluate which tools to use for the project.