Bestfolios VS Commit Together by Github

• Comprehensive Collection
  Bestfolios offers a robust and diverse collection of design portfolios, showcasing a wide variety of styles, industries, and expertise levels. This makes it a great resource for inspiration and understanding different design approaches.
• Curated Content
  The site features curated portfolios from top designers, which ensures that the showcased work meets a certain quality standard and relevance, thus making it useful for learning and growth.
• Educational Content
  In addition to portfolios, Bestfolios provides articles, case studies, and interviews with designers, offering insights into the design process, industry trends, and career advice.
• User-Friendly Navigation
  The website's interface is easy to navigate, with clear categorization and a search function that helps users quickly find the specific type of work or designer they are interested in.

Possible disadvantages

• Limited Interactivity
  The platform primarily focuses on showcasing static portfolios and lacks interactive features or community functions that could engage users more deeply or foster community interaction.
• Niche Audience
  Bestfolios is particularly geared towards designers or those interested in design, which may limit its appeal to a broader audience who are not directly involved in or interested in design-related fields.
• Risk of Homogeneity
  By showcasing primarily top portfolios, there might be a tendency towards homogeneity in styles and approaches, potentially limiting exposure to more experimental or unconventional designs.
• Commercial Bias
  There may be a potential bias towards commercial projects which are often more prominently featured, possibly overshadowing more experimental, non-commercial, or early-stage designs.

• Enhanced Collaboration
  Commit Together allows multiple authors to be credited in a single commit, which fosters a more collaborative environment and ensures everyone involved receives recognition for their contributions.
• Improved Code Review Process
  With multiple authors clearly listed, reviewers can better understand who contributed to which parts of the code, facilitating more directed questions and discussions.
• Accountability
  By attributing every change to the respective author, teams can easily track who made specific changes, which helps in accountability and understanding the history of a project.
• Efficiency in Pair Programming
  When pair programming, both developers can be credited for their combined effort, streamlining the process of sharing code ownership during collaborative sessions.

Possible disadvantages

• Complex Commit History
  Having multiple authors for a single commit may lead to a more complex commit history, making it harder to pinpoint individual contributions over time.
• Potential Workflow Conflicts
  Teams that are used to single-author commits may experience workflow conflicts or require adjustments in practices to accommodate multi-author contributions.
• Initial Setup Overhead
  Learners and new users might face a learning curve or require additional setup to understand and correctly implement the multi-author commit feature.
• Tooling Compatibility
  Some third-party tools and extensions might not fully support or display multi-author commits, leading to inconsistencies in those environments.

Tracking Bestfolios since Mar 2021.

• Ask HN: Do you rewrite pull requests?

  There is "Co-authored-by" which is supported on GitHub [1] and seems appropriate if the maintainer is basing the solution on someone's code. [1] https://github.blog/2018-01-29-commit-together-with-co-authors/. - Source: Hacker News / over 4 years ago