Follow VS Commit Together by Github

• User-Friendly Interface
  The software offers an intuitive and easy-to-navigate interface that helps users quickly adapt and efficiently manage sales and customer interactions.
• Comprehensive Features
  Follow POS provides a wide range of features such as inventory management, reporting, and customer relationship management, making it suitable for various business needs.
• Cloud-Based Access
  Being cloud-based, the software allows users to access the system from anywhere with an internet connection, facilitating remote management and real-time updates.
• Integration Capabilities
  Follow POS offers integrations with several external applications and services, enhancing its functionality and allowing seamless workflow between different platforms.

Possible disadvantages

• Learning Curve
  Although it is user-friendly, new users may still experience a learning curve when getting familiar with all the features and functionalities available.
• Cost Structure
  Depending on the size and needs of the business, the cost of using Follow POS may be relatively high, potentially discouraging smaller businesses with tight budgets.
• Connectivity Dependency
  Since it is a cloud-based system, a stable internet connection is required for optimal performance, which may be problematic in areas with poor connectivity.
• Limited Customization
  The software may offer limited customization options for businesses with unique requirements, potentially necessitating additional development or integration work.

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

Follow Review - with Tom Vasel

More videos

No Commit Together by Github videos yet. You could help us improve this page by suggesting one.

Tracking Follow 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