Profisee Platform VS Commit Together by Github

• Comprehensive MDM Solution
  Profisee Platform offers a robust master data management solution that can handle a variety of data domains, providing a comprehensive approach to data management.
• Scalability
  The platform is designed to be highly scalable, making it a suitable choice for organizations of all sizes that are looking to grow their data management capabilities.
• User-Friendly Interface
  Profisee Platform has a user-friendly interface, which makes it accessible to a wide range of users, including those who may not have extensive technical expertise.
• Flexible Deployment Options
  The platform supports various deployment options, including on-premises, cloud, or hybrid setups, providing flexibility to meet different organizational needs.
• Quick Implementation
  Profisee Platform is known for its quick implementation capabilities, which can reduce the time-to-value for organizations seeking to improve their data management processes.

Possible disadvantages

• Cost
  While feature-rich, the cost of implementing and sustaining Profisee can be significant, potentially making it less accessible for smaller businesses or those with tight budgets.
• Complexity for Small Teams
  For smaller organizations or teams, the breadth of features can be overwhelming and result in a steeper learning curve.
• Customization Limitations
  Users may face limitations when attempting to customize the platform for very niche or specific use cases, which may require workarounds.
• Integration Challenges
  Users might experience challenges when integrating Profisee with other existing systems, especially if those systems are dated or lack proper APIs.
• Dependence on Microsoft Ecosystem
  As Profisee has a significant focus on the Microsoft ecosystem, non-Microsoft environments or platforms might find it less optimized or require additional effort to integrate.

• 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 Profisee Platform since Apr 2022.

• 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