How do you monitor Dev.to and Lobsters?

Why watch Dev.to and Lobsters at all?

Matches are rare, and when one appears it is usually a tutorial, comparison or technical discussion that other developers will read and find later.

A Dev.to tutorial that uses your product is free documentation written by a user. It shows you which setup steps people struggle with and which use cases they care about. A Lobsters story about your category tends to attract a short, technical comment thread that is blunt about trade-offs.

If you sell to developers, these two sites are worth a few minutes a week. If your buyers are not developers, you can skip them.

How do you monitor Dev.to by hand?

Follow the tags that match your category, search the site for your brand and competitor names, and sort the results by newest.

Dev.to organises articles by tags, and each tag has its own page. Following a tag puts its new posts in your home feed when you sign in. Pick the tags your users write under, such as the language or database your product works with, because few authors tag an article with a vendor's name.

• Step 1: follow three to five tags for your category.
• Step 2: once a week, search Dev.to for your product name and sort by newest.
• Step 3: repeat the search for each competitor's name. Comparison posts ('I tried X and Y') often name both.
• Step 4: when you find a tutorial that uses your product, read it start to finish and note any step where the author had to work around your docs.

How do you monitor Lobsters by hand?

Watch the newest stories and the tags for your area, and search by name for your product and competitors.

Lobsters is a link aggregator with a small, invite-only membership. Members are invited by existing members, and the invite tree is public. Every story carries at least one tag, so the tags for your language, platform or topic are the easiest way to follow your category.

Volume is low enough to scan the newest stories in a couple of minutes. Run the site search for your product and competitor names now and then, and read the comment threads on any story in your category, since that is where tools get compared.

How should a company take part on Dev.to and Lobsters?

On Dev.to, publish tutorials that teach something and comment as yourself; on Lobsters, take part as an individual member and keep self-promotion to a small share of what you post.

The two sites have different norms. Dev.to welcomes posts from people who build products, as long as the post teaches something. Lobsters members are wary of posts that read like marketing, and the community expects members to contribute more than links to their own work.

What does MarketHQ cover on Dev.to and Lobsters?

On every plan, from Lite at $29 a month, MarketHQ matches your terms in Dev.to article titles, descriptions and tags, and filters Lobsters' newest stories for them.

Both sources sit in the same feed as Hacker News, GitHub, Stack Overflow, blogs and RSS feeds you add. Every plan checks them four times a day, keeps the last 30 days of posts, and sends a weekly summary email; Lite tracks two competitors and ten keywords. A daily Slack digest of top reply opportunities is available on any plan.

Be clear about the gaps. MarketHQ does not read full Dev.to article bodies, so a post that names you only in paragraph six will not match; a periodic manual search covers that. On Lobsters it filters the newest stories, so read the comment threads on stories in your tags yourself. Matching works on word boundaries, so a product with a common word as its name should add a qualifying keyword.

What does a month of Dev.to and Lobsters matches look like?

Illustrative example: a handful of matches, one docs fix, one thank-you comment and one thread worth reading closely.

Illustrative example: a company selling a Postgres migration tool sees three Dev.to matches in a month. One is a tutorial that uses its CLI and works around a missing flag; the team thanks the author in the comments and adds the flag to its docs. The second is a 'tools I use' list, which they log. The third compares them with a competitor and gets the pricing wrong, so they leave a short, disclosed correction. On Lobsters, one story about schema migrations collects a comment thread debating their approach against a competitor's, and they copy the two main objections into their positioning notes.

When are Dev.to and Lobsters not worth monitoring?

When your buyers are not developers, or when you will not act on what you find.

Both sites are small, and a company outside software may see no relevant matches for months. Even for developer tools, volume is low, so do not judge your community presence by these two alone. Hacker News, GitHub, Stack Overflow and, on paid plans, Reddit usually carry more of the conversation.