Hey From The Future VS Commit Together by Github

• Innovative Concept
  Hey From The Future provides a unique platform for users to send messages to themselves or others in the future, which can be a fun and creative way to make predictions or set goals.
• Personal Development
  The service encourages self-reflection and personal growth by allowing users to reflect on their past thoughts and aspirations upon receiving their future-directed letters.
• Creative Gift
  This platform can be used to send thoughtful and creative messages or gifts to friends and loved ones on significant dates in the future, providing an element of surprise and nostalgia.

Possible disadvantages

• Uncertainty of Delivery
  There is a risk that messages may not be delivered due to changes in contact information or digital services over time, which can lead to disappointment.
• Privacy Concerns
  Sending personal messages for future delivery may raise privacy concerns, as users have to trust the platform with sensitive information over an extended period.
• Limited Audience Appeal
  The concept may not appeal to everyone, as some people might not see the value in sending messages to the future or may prefer traditional forms of communication.

• 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.

• Older people always say they want to be young again. Well, I am young. What do I do?

  There's this website which you mind find helpful Https://heyfromthefuture.com/. Source: over 4 years ago

• What would you tell your teenage self?

  I'd send them this link: https://heyfromthefuture.com/. Source: over 5 years ago

• 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