Skip to content

Conversation

@tessamero
Copy link
Contributor

@tessamero tessamero commented Nov 6, 2025

What does this PR do?

image

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

  • Documentation
    • Added a comprehensive new blog post on developer experience (DX) metrics and retention. Covers a DX metric model (north star plus four leading indicators: TTFD, FASR, TTFDp, W4PAR), benchmark guidance, practical instrumentation steps, definitions and touchpoints, cited sources, and a structured weekly DevRel + DX review ritual to drive measurement and program improvements.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 6, 2025

Walkthrough

A new blog post file was added at src/routes/blog/post/the-developer-experience-data-that-actually-predicts-retention/+page.markdoc. It contains front-matter metadata (layout, title, description, date, cover, timeToRead, author, category, featured) and static Markdoc content describing a developer-experience metric model, leading indicators (TTFD, FASR, TTFDp, W4PAR), benchmarks, instrumentation guidance, and a suggested weekly DevRel + DX review ritual. No executable code, exported/public API changes, or programmatic logic were introduced.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Verify front-matter fields are valid and formatted correctly.
  • Quick scan of markdown for rendering issues (links, images, headings, lists).
  • Confirm file path and naming follow blog conventions.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: adding a blog post about DX metrics that predict retention, which directly matches the static content addition in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch tessa-firebase-blog-post

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b6f844c and 233e83a.

📒 Files selected for processing (1)
  • src/routes/blog/post/the-developer-experience-data-that-actually-predicts-retention/+page.markdoc (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/routes/blog/post/the-developer-experience-data-that-actually-predicts-retention/+page.markdoc
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: build
  • GitHub Check: assets
  • GitHub Check: tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd85057 and 7a60baa.

⛔ Files ignored due to path filters (1)
  • static/images/blog/the-developer-experience-data-that-actually-predicts-retention/cover.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • src/routes/blog/post/the-developer-experience-data-that-actually-predicts-retention/+page.markdoc (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: build
  • GitHub Check: tests

…ly-predicts-retention/+page.markdoc

Co-authored-by: Aditya Oberai <[email protected]>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

♻️ Duplicate comments (1)
src/routes/blog/post/the-developer-experience-data-that-actually-predicts-retention/+page.markdoc (1)

34-34: Apply the link formatting fixes from previous reviews.

The inconsistent link formatting issues at lines 34, 72, 103, and 136 have been flagged in previous reviews with detailed fixes. Please apply those suggested changes to convert plain URLs in parentheses to proper markdown links.

Also applies to: 72-72, 103-103, 136-136

🧹 Nitpick comments (1)
src/routes/blog/post/the-developer-experience-data-that-actually-predicts-retention/+page.markdoc (1)

124-124: Consider summarizing the lengthy quote.

The quote from Mary Thengvall, while valuable, is quite long and takes up most of the paragraph. You might consider paraphrasing the key points and using a shorter direct quote for emphasis.

For example:

**DevRel qualified leads**  
Adopt DRQL so DevRel is evaluated on enablement and introductions rather than quota. This keeps trust with developers and still ties to revenue via the DX indicators. As Mary Thengvall explains, tracking DevRel Qualified Leads provides "a definitive way to attribute value to the activities that the DevRel team is involved in" and helps identify which activities are most effective over time. Source: [Mary Thengvall](https://www.marythengvall.com/blog/2019/12/14/devrel-qualified-leads-repurposing-a-common-business-metrics-to-prove-value).
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7a60baa and 6282985.

📒 Files selected for processing (1)
  • src/routes/blog/post/the-developer-experience-data-that-actually-predicts-retention/+page.markdoc (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: build
  • GitHub Check: tests

@adityaoberai
Copy link
Member

@tessamero not sure if it's just me but does it seem like these quotes overpower our own content? Ideally, these should complement what we're adding, not necessarily replace it

image image

Maybe we can paraphrase these and link the appropriate sources accordingly, otherwise these interfere with the reading experience

@adityaoberai
Copy link
Member

@tessamero what do you think about adding bullets to these points?

image

# A weekly DevRel plus DX review ritual

> Feedback loops… focused on the speed of answering questions and completing code reviews… have positive impacts at the team level.
Source: Microsoft DevEx Lab (https://azure.microsoft.com/en-us/blog/quantifying-the-impact-of-developer-experience/).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Source: Microsoft DevEx Lab (https://azure.microsoft.com/en-us/blog/quantifying-the-impact-of-developer-experience/).
Source: [Microsoft DevEx Lab](https://azure.microsoft.com/en-us/blog/quantifying-the-impact-of-developer-experience/).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants