Watch People Code VS Commit Together by Github

• Learning Opportunity
  Watch People Code provides a platform for learners to see real-time coding practices, offering a practical learning experience by observing how experienced programmers solve problems and write code.
• Skill Improvement
  By watching others code, individuals can expose themselves to new coding techniques, languages, and tools, thereby improving their skillset and broadening their coding knowledge.
• Community Engagement
  The platform fosters a community of like-minded individuals who are interested in coding, allowing users to share tips, ask questions, and engage in discussions, enhancing the communal learning experience.
• Real-World Application
  Observing live coding sessions provides insight into real-world applications of coding concepts, helping viewers understand how theoretical knowledge is applied in practice.

Possible disadvantages

• Information Overload
  For beginners, watching live coding might be overwhelming due to the complexity and pace, which can lead to confusion and difficulty in understanding the content being presented.
• Lack of Structure
  Unlike structured courses or tutorials, the content on Watch People Code can be unorganized, making it challenging for viewers to follow along or learn systematically.
• Variable Quality
  The quality of coding demonstrations can vary greatly depending on the skills and experience of the streamer, leading to inconsistencies in educational value and effectiveness.
• Time-Consuming
  Live coding sessions can be lengthy, requiring a significant time commitment from viewers, which might not be feasible for everyone, especially if they are looking for quick learning resources.

• 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 Watch People Code 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