Get to the point!

Nobody likes a lecture.

“Get to the point!” said my daughter, exasperated.

I’d tell you the full story, but I want to honor her wishes.

And I’ve heard similar feedback on people scrolling down these weekly newsletters to find the point.

No scrolling needed for this one—I’ll get to the point!

In most cases, developers also want you to get to the point:

• Tell them what’s possible, without marketing fluff
• Help them see it for themselves with quick starts
• Share use cases, not vague feature-rich promises
  ​

Is there still a need for long-form content? Absolutely. And when it educates and inspires solutions, developers won’t complain about whether you get to the point.

As for the rest of your content, you can typically skip the lengthly preamble and flowery overture: just get to the point.

Now… I started with the point of this newsletter…

And it’s not to promote the book I wrote, though you’ll find it contains the philosophy that helps attract and hold the interest of developers.

And you’ll need to know what a developer wants before you know what point you need to get to.

Like most of these newsletters I share with you, the book includes some stories.

Each story has a point that explains each element of developer content. And people appreciate them, too:

If you’d like help to figure out how to get to the point with developers: start with the book, then reach out to the EveryDeveloper team.

P.S. And if you’d like more stories, including behind-the-scenes of why I included certain elements in the book, listen to my short podcast episodes. Each is 3-7 minutes long and follows the structure of Developer Marketing Does Not Exist.