<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: mud</title>
    <description>The latest articles on DEV Community by mud (@muddysnow).</description>
    <link>https://dev.to/muddysnow</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3967422%2F61b355d2-6ff6-4b94-91e6-99a0091fd071.jpeg</url>
      <title>DEV Community: mud</title>
      <link>https://dev.to/muddysnow</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/muddysnow"/>
    <language>en</language>
    <item>
      <title>Website feedback needed</title>
      <dc:creator>mud</dc:creator>
      <pubDate>Thu, 04 Jun 2026 05:15:35 +0000</pubDate>
      <link>https://dev.to/muddysnow/website-feedback-needed-57k0</link>
      <guid>https://dev.to/muddysnow/website-feedback-needed-57k0</guid>
      <description>&lt;p&gt;Hello,&lt;br&gt;
I am currently building a service that automatically organizes a developer’s project history and development style based on GitHub activity data.&lt;br&gt;
The service is still in the refinement stage, so I wanted to ask for feedback from actual developers on whether this approach feels useful from a developer’s perspective.&lt;br&gt;
The core feature of the service is that when a user connects their GitHub repositories, the service analyzes activity data for each repository and automatically generates a project summary.&lt;br&gt;
For example, each project includes information such as:&lt;br&gt;
Project activity period&lt;br&gt;
Last updated date&lt;br&gt;
Number of commits&lt;br&gt;
Lines of code added/deleted&lt;br&gt;
Number of changed files&lt;br&gt;
Main tech stack used&lt;br&gt;
Summary of the project’s characteristics&lt;br&gt;
In other words, instead of requiring users to write project descriptions from scratch, the service automatically creates portfolio-style project cards based on GitHub activity records.&lt;br&gt;
It also analyzes the technologies the user has actually used on GitHub and automatically categorizes tech stacks such as React, TypeScript, Python, Docker, and others. It shows how long each technology has been used and how many projects it appears in.&lt;br&gt;
Additionally, the service provides a developer style analysis based on Git activity patterns.&lt;br&gt;
For example, it visualizes metrics such as agility, stability, contribution level, adaptability, and activity level, then summarizes the user’s development style as a certain type.&lt;br&gt;
The part I am currently thinking about the most is how much users should be able to edit the automatically generated results.&lt;br&gt;
To maintain data credibility, repository-level project summaries and tech stacks are generated based on GitHub activity, and currently users cannot directly edit them.&lt;br&gt;
This could increase trust because the results are based on actual activity data. However, it could also be inconvenient because users may not be able to describe their own projects in the way they want.&lt;br&gt;
So I would like to ask developers for feedback on the following points:&lt;br&gt;
Would an automatically generated portfolio based on GitHub activity actually feel useful to you?&lt;br&gt;
If repository-level project summaries are automatically generated and cannot be directly edited, would that make the results feel more trustworthy, or would it make the portfolio less useful?&lt;br&gt;
Would an automatically organized tech stack based on real GitHub activity be helpful for resumes or portfolios?&lt;br&gt;
Do developer style analysis metrics such as agility, stability, contribution level, adaptability, and activity level feel meaningful to you?&lt;br&gt;
Do you think these analysis results could be used for personal portfolios, LinkedIn, resumes, or team building?&lt;br&gt;
If connecting a GitHub account feels burdensome, what would be the biggest reason?&lt;br&gt;
This is closer to a feature validation stage than a promotional post.&lt;br&gt;
As shown in the attached images, I am working on screens for repository-level summaries, tech stack analysis, and developer style analysis. I would really appreciate honest feedback on what feels awkward, what feels useful, and what could be improved from an actual developer’s point of view.&lt;br&gt;
Thank you.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>github</category>
      <category>showdev</category>
      <category>sideprojects</category>
    </item>
  </channel>
</rss>
