How do you describe a developer tools?

Re:How do you describe a developer tools? by sha666sum on Thursday August 29, 2019 @06:28PM (#20834343)

While I'm not at all familiar with the stack your tool is for and have no qualifications whatsoever to give solid advice on this:

My cynical impression is that the vague punchlines are meant to impress middle management, but if you want to win over developers, it's best to be straightforward. From my point of view (which is an amalgamation of Linux nerd, security & FOSS advocate and Windows gamer), I'm going to bounce right away from your webpage if it doesn't give me a clear description of what the product is about. The entire internet competes for my attention, so if your website contains stock photos of smiling office workers who are "working smarter", I'm going to press Ctrl + W quite fast. Having said that, I have no issue with "Leverage GraphQL + Serverless in data-driven SaaS apps". It's honest about what your product is about, and in my experience honesty correlates with other good properties of software.

I had a look at how Microsoft markets some of their developer products, and I think their messaging is on point here[1]:

- Visual Studio IDE

Rich IDE, advanced debugging

- Visual Studio Code

Editing and debugging on any OS

- Azure DevOps

Agile tools, Git, continuous integration

- Visual Studio App Center

End to end developer services for mobile and desktop apps

[1] https://visualstudio.microsoft.com/

[ Parent | on HN ]

Re:How do you describe a developer tools? by sebscholl on Friday August 30, 2019 @10:55AM (#20839213)

This is actually super useful sha666sum! It's interesting looking at the difference between the two too. Where Visual Studio IDE is super direct, and Visual Studio spans a number of use cases. I feel like that's where I'm getting caught in the middle of.

[ Parent | on HN ]