Stratechery VS Commit Together by Github

• Insightful Analysis
  Stratechery provides deep and comprehensive analysis of technology and media businesses, offering insights that are valuable to industry professionals.
• Expert Commentary
  The content is written by Ben Thompson, who is well-regarded in the tech industry for his expert understanding of business strategy and market dynamics.
• Regular Updates
  Subscribers receive multiple updates each week, ensuring they are always up-to-date with the latest developments and trends in the tech industry.
• Focus on Business Strategy
  The platform focuses on the intersection of technology and business strategy, providing a unique perspective that blends technical knowledge with strategic insights.

Possible disadvantages

• Subscription Cost
  Stratechery operates on a subscription model, which may not be affordable for everyone interested in its content.
• Niche Focus
  The analysis is heavily focused on technology and media companies, which may not appeal to individuals outside these sectors.
• Content Density
  The articles and updates can be quite dense and detailed, which might be challenging for casual readers or those unfamiliar with the subjects.
• Limited Free Content
  There is limited free content available, so potential subscribers have minimal opportunity to sample the material before committing financially.

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

Ben Thompson, founder of Stratechery | Code 2018

More videos

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

• Rubio orders return to Times New Roman font over 'wasteful' Calibri

  > Does anyone else like to change the font on news articles using Inspect Element? Yes, for sites that use unreadably thin fonts, such as https://stratechery.com. - Source: Hacker News / 9 months ago

• Ask HN: What computer science blogs do you have bookmarked?

  Stratechery (https://stratechery.com) These are basically all ML/AI blogs except Ludicity. Any others I should add? - Source: Hacker News / over 1 year ago

• Magic/tragic email links: don't make them the only option

  1. Indirect security downsides. Pushing people to access personal email on work devices (or vice-versa) isn't exactly a win for security. Another annoying _passwordless_ system is to email or SMS an OTP the end user can type in. While... - Source: Hacker News / over 1 year ago

View more

• 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