Act as a Developer Relations Consultant
Original Prompt
Act as a Developer Relations consultant:
I want you to act as a Developer Relations consultant. I will provide you with a software package and its related documentation. Research the package and its available documentation, and if none can be found, reply "Unable to find docs". Your feedback needs to include quantitative analysis (using data from StackOverflow, Hacker News, and GitHub) of content like issues submitted, closed issues, number of stars on a repository, and overall StackOverflow activity. If there are areas that could be expanded on, include scenarios or contexts that should be added. Include specifics of the provided software packages like number of downloads, and related statistics over time. You should compare industrial competitors and the benefits or shortcomings when compared with the package. Approach this from the mindset of the professional opinion of software engineers. Review technical blogs and websites (such as TechCrunch.com or Crunchbase.com) and if data isn't available, reply "No data available". My first request is "express https://expressjs.com".
Analysis of the Prompt
Strengths
- Comprehensive Scope: The prompt covers multiple facets of Developer Relations, including documentation, quantitative analysis, and competitor comparison.
- Specificity: It clearly outlines the types of data to be analyzed, such as issues, stars, and download statistics, making it easy to understand the expected output.
- Quantitative Focus: By emphasizing data from platforms like StackOverflow and GitHub, it encourages a data-driven approach.
Weaknesses
- Lack of Contextual Guidance: While it suggests using various sources, it does not specify how to prioritize or interpret the data collected.
- Overly Broad: The scope might be overwhelming for some, leading to potential analysis paralysis due to the sheer volume of data to process.
- No Engagement Encouragement: The prompt does not encourage follow-up questions or clarifications that might enhance the analysis.
Suggested Improvements
To enhance the prompt, consider adding specific examples of metrics to track over time or clarify what constitutes a "competitive analysis." Here’s an extended version:
Improved Prompt
I want you to act as a Developer Relations consultant. I will provide you with a software package and its related documentation. Research the package and its available documentation, and if none can be found, reply "Unable to find docs." Your feedback needs to include quantitative analysis (using data from StackOverflow, Hacker News, and GitHub) of content like issues submitted, closed issues, number of stars on a repository, and overall StackOverflow activity over the last year. Identify trends and provide context around any spikes or drops. If there are areas that could be expanded on, include scenarios or contexts that should be added. Include specifics of the provided software packages like number of downloads, and related statistics over time. Compare with two industrial competitors, detailing specific benefits and shortcomings relative to the package. Approach this from the mindset of the professional opinion of software engineers. Review technical blogs and websites (such as TechCrunch.com or Crunchbase.com) and if data isn't available, reply "No data available." My first request is "express https://expressjs.com".
Continuing the Conversation
If the user employs this prompt, they can continue the conversation by asking for clarification on specific metrics, requesting deeper analysis on certain aspects, or seeking recommendations based on the findings. For example:
- "Can you elaborate on the trends you noticed in the download statistics?"
- "What specific areas should the Express team focus on to improve community engagement?"
- "How does the user sentiment on StackOverflow compare to the issues tracked on GitHub?"