Code Time VS Commit Together by Github

• Productivity Tracking
  Code Time provides detailed analytics on your coding habits, helping developers track their productivity and identify patterns that can improve efficiency.
• Integration
  The tool integrates seamlessly with popular code editors like VS Code, Sublime Text, and Atom, making it convenient to use without disrupting existing workflows.
• Goal Setting
  It offers features like setting coding goals and measuring progress, which can motivate developers to stay on track and achieve their objectives.
• Free Version
  Code Time offers a free version with ample features, making it accessible to individual developers and small teams who might have budget constraints.
• Cross-Platform Support
  Available on multiple platforms, Code Time allows developers to use it on their preferred operating systems, ensuring flexibility and ease of use.

Possible disadvantages

• Privacy Concerns
  Since Code Time tracks coding activity, there may be concerns regarding data privacy and how the information collected is used or stored.
• Limited Advanced Features
  While the free version is robust, some advanced features are locked behind a paywall, which might deter users looking for a comprehensive free tool.
• Potential Distractions
  The continuous tracking and notification features might become distracting for some developers, causing interruptions in focus during coding sessions.
• Learning Curve
  New users may experience a learning curve as they navigate through the various features and settings, especially those unfamiliar with productivity tools.
• Dependence on IDE
  Code Time is dependent on the use of supported integrated development environments (IDEs), potentially limiting its usefulness for developers who use less conventional coding setups.

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

• How do you prevent PRs from getting stuck in your teams?

  There are some tools like software.com's devtools suite. It can surface all your throughput metrics as well as give you a "pending reviews" view to see what's waiting. You can also set it up to ping you with things sit around for too long. Source: almost 4 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