someproduct

We’ve put together a catalog of hosted MCP servers on the Posmtan API Network to help devs discover and test servers using the Postman client. Would love feedback.

Hey Abhinav, DX is such a critical component to a successful API, and historically "developer" has meant "human." As agents become important consumers of APIs, what are your thoughts on how DX evolves? Is "agent experience" or "machine experience" different than developer experience?

If anyone else is wondering, TIL the spelling “Hallowe’en” on a number of these postcards is a contraction of “All Hallows’ Even," and that "even" was a common term for "evening" in Old and Middle English.

Thanks for sharing this. Without having any more context, here are some thoughts to consider:

- are there rituals that your community observes together?

- are there milestones community members can achieve that signify their progress or tenure?

- are you regularly acknowledging and celebrating folks who are contributing and adding a lot of value?

- have you tried casual events to connect members to one another?

- what is the unifying sense of identity that could/should bind everyone together? Can you lean into that?

Thanks for mentioning this. Truth is I don't exactly remember. I'd say the first 10–20 were friends and former colleagues. Definitely people we directly reached out to and invited to the Slack.

There was also early interest around a framework we created called the Orbit Model[1], which at that point existed primarily in blogpost form.

Before starting Orbit, we did consulting[3] in the developer relations/developer marketing space for about a year, and had met a lot folks who were thinking about the challenges we sought to address, so that group of clients and prospects definitely provided the seeds for the early community.

But yeah, to your point: content can be a great way to attract like-minded folks to an early community. We certainly saw that with the combination of our blog + the Orbit Model.

[1] https://github.com/orbit-love/orbit-model [2] https://orbit.love/blog/why-orbit-is-better-than-funnel-for-... [3] https://developermode.com/

Thanks! We definitely could've started with events sooner, IMO. The simple practice of getting folks together to meet and talk shop contributed to the sense of momentum overall and the interpersonal connections in particular.

I should note that all the events we've done to date have been small, and focused on our existing community. I think such focus made sense for us in year one, since we were building the community and the product at the same time. In other words, we didn't have the capacity to produce a broadly-focused event.

That said, the intimate vibe in the early days goes a long way toward engendering a sense of ownership and belonging among community members. I honestly think it's more meaningful to do smaller insider events more frequently in the early days, versus casting a brand net and potentially diluting the group’s nascent identity and culture norms.

Now that we're scaling up, I anticipate increasing the reach of our events as well. But that’s okay, as we have the team to support it on one hand, and on the other, the culture of the community is already well-defined.

First day? Maybe 5 people we harangued into joining?

As for the first three months, it depends on when we start counting (I'd say May represented the first month we actually started working on community deliberately), but had 59 by end of July.

You can see the growth curve here: https://res.cloudinary.com/dzello/image/upload/v1615409348/s...

I think this could and should be generalized into "Avoid surprises"

Great way of putting it. When we were considering moving our community from Slack to Discord[1], we actually did a Request for Comment[2] laying-out our rationale, and asked for comments on the doc. I think this went a long way towards building trust and buy-in around big community decisions.

1. https://orbit.love/blog/how-to-migrate-a-community-from-slac...

2. https://docs.google.com/document/d/1PFHhZyyYmiIHNufYpS6fX7gU...

Author of the post here. Happy to answer any questions!

"We used the word "love" a lot at DigitalOcean as one of the key/core values for how we thought about customers and community. "

Right on! We think the language we choose for our frameworks has many downstream effects, and we specifically use "Love" (versus something like “engagement”) in the Orbit Model: https://github.com/orbit-love/orbit-model

"how do you think of blogs and content marketing w.r.t this? Is that a "big marketing effort" or does it fit into community?"

There’s definitely lots of overlap between content and community, and generally we don’t try to draw hard lines, as context matters so much.

For the purposes of this question, though, we can think in terms of a spectrum. On one end, all content would be community-generated, and on the other, all content would be produce and distributed by the company.

In most cases, you’ll have a mix of both.

In the case of NRG, the formula discussed in the article, the question is “how fast are we growing before layering on incremental investments in sales and marketing.”

For the purposes of this metric, I think the spirit of the law would say that company-generated content would fall outside of scope, but stuff that folks in the community were organically creating could reasonably be included.

Author of the post here. We compared each platform across ~25 factors, looking specifically at their utility for communities of different shapes and sizes.

I've found the book "New Kingmakers: How Developers Conquered the World" really instructive on this point.

It focuses on the "rise of the developer," if you will, as an influential decision-making and budget-holding role within a company. It also includes lots of perspective on appealing to developers and avoiding marketing and business jargon.

As a nontechnical founder myself, it's been really helpful.

Author here, thanks for the question.

For one we thought they'd care about TAM — most did, but the way the cared differed. In other words, some immediately required a firm answer to "How can this become a billion-dollar business," while others asked questions that seemed to pressure test our hypotheses and assumptions, but were more interested in quality of thought rather than our ability to see the future.

We thought they’d care about product mockups, but most didn’t. My assumption is that they knew it would all change drastically (they were right).

They did care a lot about how prior experiences would confer advantages, so we ended up leaning into that heavily the more we pitched.

You realize that's just a screen grab of The Wolf of Wall Street, right?

I think what you say is true, but only if you somehow arrive on a website with absolutely no understanding of what you're looking at or how you arrived there.

When most people land on a company's home page, they arrived there from searching specific keywords in a search engine (which demonstrates a context for what they're searching for), clicking-through a socially shared link (which probably includes descriptive text like "Checkout this awesome Fireworks replacement I've been using...), or directly clicking marketing messages in an email or display ad (in which case they'll have a very clear understanding of the category the company is in).

In other words, they have a pretty good sense of "what this thing is," and they want to know _why_ it's better than the other ones they've seen.

Now, if you click a link on HN that says something like "I'm 13! Checkout the product I coded over the weekend!" then yes, the main question will be "what is this thing?" But in the "real world," people don't often stumble randomly across websites in this way, and if they do, they're probably not in the target audience anyway.

Most of the time (and I'm assuming we're all optimizing for most of the time instances), users already know generally what you do. So tell them why you do it in a way that is interesting and meaningful.

Great thought. I'll write a followup with some good examples.

> What's behind the company name is the idea of uncovering your company/employees potential.

This crucial point about your brand isn't conveyed anywhere in the homepage copy. Making that connection to unify the solid URL with your core benefits in the copy will go a long way toward telling a cohesive story about not only what you do, but why you do it.

I've found that the weakest part of many presentations is in the transition from one point or idea to the next.

Shaky transitions are a prime cause of audience disinterest, and poor flow can quickly remove the auditor from the energy and flow the speaker has established, which makes such a time perfect for checking twitter and FB and otherwise disengaging.

The boundaries between ideas should feel natural and smooth, and I think for many it's difficult to arrive at a natural transition without getting very intentional about it, i.e. writing it out.

So I say write it down, edit, speak chunks out loud, and edit more.

In this way, the presenter can craft the most important sections with style while becoming familiar enough with the material that the delivery feels quite natural.

HN links aside, you almost certainly wouldn't arrive at everlane.com without any context or understanding.

Most first-time visitors probably come from something social, and thus have a pretty good idea that Everlane is some kind of retail.

Knowing this, the folks at Everlane opted to optimize the band experience for registered users and those who haven't registered but are familiar with the company. This is a great example of leveraging a point-of-view into a statement about your brand, rather than watering-down the messaging to appeal to even the smallest subset of users.

This is a wonderful example of interface as brand. Logos are such a small piece of online brands, and it's cool to hear that folks at eBay grasped this so early. Thanks a ton for sharing!

In short, go to things. Lots. I've talked about this a bit here: http://bit.ly/MbQOkf

If there are no things, start hosting.

"Member of the founding team" is the verbiage that's been bandied about, but not entirely certain what that means yet.

Your response has been very helpful. Thank you.