AMS360 VS Commit Together by Github

• Comprehensive Features
  AMS360 offers a wide range of features including customer management, policy management, and financial tracking, providing an all-in-one solution for insurance agencies.
• Integration Capabilities
  The platform integrates well with other Vertafore products and third-party applications, allowing for seamless data flow and improved operational efficiency.
• User-Friendly Interface
  AMS360 boasts an intuitive and easy-to-navigate interface that can help reduce the learning curve for new users.
• Strong Customer Support
  The platform is backed by reliable customer support services, including training resources and a dedicated support team to assist with any issues.
• Cloud-Based Solution
  Being a cloud-based system, AMS360 offers the flexibility of accessing data and managing operations from any location with internet access.

Possible disadvantages

• Cost
  The pricing structure of AMS360 might be expensive for smaller agencies, especially those that do not require all of its features.
• Customization Limitations
  Some users may find that the platform’s customization options are limited, which could restrict the ability to tailor the software fully to their specific needs.
• Complexity for New Users
  Despite its user-friendly interface, the extensive capabilities of AMS360 might overwhelm new users initially, requiring significant time to fully understand all features.
• Performance Issues
  Some users have reported occasional performance issues, such as slow loading times or system lags, which could disrupt workflow.
• Data Migration Challenges
  Migrating data from other systems into AMS360 may present challenges, potentially requiring additional time and resources to ensure accuracy.

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

AMS360 Appending Activities and Documents

More videos

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

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