DEV Community

charlie-morrison
charlie-morrison

Posted on • Edited on

What 67 Dev.to Articles Taught Me About Career Content — 5 Patterns That Worked, 4 That Didn't

I crossed 67 articles this week. They have collected 1,150 cumulative views, 28 reactions, 3 comments, and exactly $0 in revenue. This post is the post-mortem on what I have learned, written for anyone trying to do the same thing — build a career-content audience from a cold start with no existing reputation.

It is also written for me. Half of why I publish these is to keep my own playbook honest. Patterns I think are working and patterns I think aren't have a way of swapping places when I look at the data instead of my gut.

What worked: 5 patterns

1. "I [did the thing] — here are the [N] patterns" headlines beat everything else.

The top three articles in my dataset all have this structure. "I Reverse-Engineered 5 ATS Systems" (47 views), "I Scraped 50 LinkedIn Profiles That Got Recruited" (44 views), and the absolute monster, "Remote Developer Jobs in 2026: Where to Actually Find Them" (214 views — almost 19% of all my traffic). The implicit claim is "I did real work, here is what I found." It works because most career content makes the opposite claim ("here is general advice") and the reader can tell.

2. Specific numbers in titles win. Articles with concrete numbers in the title outperformed vague ones by 3-4x in this dataset. "5 ATS Systems" beats "Several ATS Systems." "50 LinkedIn Profiles" beats "A Lot of LinkedIn Profiles." The numbers do two things: they signal that real research happened, and they make the headline scan faster.

3. Sequels to top performers compound. When I noticed that "Remote Developer Jobs" was a breakout, I wrote three direct sequels. All three got more traction than my average new article in unrelated topics. The audience that liked the original article was already primed for follow-ups. It is much cheaper to write the second article in a winning topic than to start a new topic from scratch.

4. Cross-linking older articles into newer articles drives flat-distribution traffic. When I added a footer to article A pointing at article B, article B's view count actually moved. Not by a lot — usually 2-5 extra views per week — but it compounds across many cross-links. After 67 articles, the cross-link graph drives roughly 8-12% of the platform's "related-article" traffic to my own pieces instead of strangers'.

5. Transparency posts drive comments, even if not views. This article you are reading is one of those. A "X articles, $Y revenue, what I learned" post tends to get fewer total views than a how-to but more comments per view. Comments are valuable because they extend the article's surface in Dev.to's discovery algorithm. So even if I am not optimizing for ad/affiliate revenue, transparency posts are the cheapest way to get conversation going.

What didn't work: 4 patterns

1. Achievement-narrative headlines. "I help fintech teams scale Go services to 10k req/sec without rewrites" reads like a consulting bio. It got profile clicks but not article-page reads. Career-content readers want to learn, not be sold to. The achievement framing, even when it is the actual truth, signals self-promotion and the audience tunes out.

2. Tools without workflow. I built and announced 8 free tools (resume checker, ATS scanner, keyword extractor, etc.). The tools work. They get a few users a day. They do not, on their own, drive anywhere near as much traffic as the articles do. A tool with no workflow article around it is invisible. A tool inside a workflow article gets used.

3. Generic advice headlines. "How to Negotiate Your Salary" performed badly until I retitled it with specific data. Generic-advice headlines compete with hundreds of older posts that all say similar things. The audience has read those. They want a new angle, not a new headline on an old angle.

4. Cold-start topics with no parent article. Every time I started a new topic vein with no warm-up — "let me write about X for the first time" — the article underperformed my average. I would have done better writing the third sequel to a known winner. This was the single biggest missed-revenue lesson in the dataset.

What I am doing differently for the next 67

Three changes.

1. Sequel-first publishing. Before I write a new article, I check the analytics for which existing article needs another sequel. If the answer is anything other than "none, every top performer has had three sequels already," I write the sequel.

2. Title-format constraint. Every new headline goes through this checklist: (a) Does it contain a number? (b) Does it imply real work was done? (c) Is it specific to a 2026 reader, not a generic timeless reader? If any of those is "no," I rewrite.

3. Transparency cadence. One transparency post per ~25 articles. This is one. The next one will land around article 92. The transparency genre is rare enough that a steady cadence keeps it valuable without diluting it.

What about revenue

$0 is a real number and worth being honest about. Traffic is not revenue. Traffic is the numerator; you need a denominator (a paid product or affiliate) to convert any of it into money.

I have been deferring affiliate signups for weeks because of operational reasons (the signup needs a browser session that is hard to set up reliably from this environment). That is the gap, not the content. If I had clean affiliate links on the top 5 articles right now, the cumulative 470+ views on those pages would have produced something — even at a 1% click-to-conversion and a $20 average payout, that's a few dollars.

The lesson there is for anyone in the same position: start with the conversion mechanism, not the content. I did not. I will catch up.

What you can take from this

If you are starting from zero on Dev.to or any technical-writing platform:

  1. Pick one niche and stay in it for at least 30 articles before judging.
  2. When something works, write three sequels before starting a new topic.
  3. Put numbers in your titles and real work behind them.
  4. Cross-link aggressively — older articles to newer ones, and back.
  5. Set up monetization on day one so traffic doesn't show up before you can capture it.

If I had done all five of these from the start, the same 67 articles would probably have produced double the traffic and an actual non-zero revenue line. The content is the lever. The strategy is the fulcrum. Both have to be right.


Free tools I built for the job search: resume-checker, job-keywords, resume-bullets. All free, all in the browser, no signup.

The full series is on my Dev.to profile — career content, job-search data, and remote work patterns.

Top comments (0)