Voice Notes VS Commit Together by Github

• Ease of Use
  Voice notes allow for quick and easy capture of information without the need to type, which can save time and improve efficiency.
• Capturing Nuance
  Voice can capture tone and emotion in ways that text cannot, providing richer context to the notes.
• Accessibility
  For individuals who may have difficulty typing due to physical constraints or disabilities, voice notes offer an accessible alternative.
• Multitasking
  Voice notes allow users to record ideas or information while engaging in other activities, aiding in productivity.

Possible disadvantages

• Noise Interference
  Background noise can interfere with the clarity of voice recordings, making it difficult to understand the captured audio.
• Privacy Concerns
  Recording voice notes can pose privacy issues, as sensitive information could be captured inadvertently if not handled securely.
• Searchability
  Voice notes are less searchable compared to text-based notes, making it more challenging to quickly find specific information.
• Storage Space
  Audio files can take up more storage space than text notes, potentially leading to storage issues on devices with limited capacity.

• 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 Voice Notes 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