Commandline Challenge VS Commit Together by Github

• Skill Enhancement
  The Commandline Challenge helps users improve their command-line skills by offering a practical and engaging way to practice and learn new commands.
• Immediate Feedback
  Users receive instant feedback after submitting their solutions, which helps them quickly identify mistakes and learn from them.
• Variety of Challenges
  The platform offers a wide range of challenges that cater to different skill levels, from beginners to advanced users.
• Browser-Based
  Since the challenges are browser-based, there is no need for users to install any additional software to participate.
• Community Engagement
  Users can see solutions from other community members, which can provide new insights and alternative problem-solving approaches.

Possible disadvantages

• Limited Scope
  The challenges are limited to specific command-line tasks and may not cover a comprehensive range of topics or tools found in real-world scenarios.
• No Real-World Environment
  Since the exercises are conducted in a controlled environment, users may not experience real-world complexities and challenges faced when using command-line tools.
• Lack of Detailed Explanations
  The platform may not provide detailed explanations or learning materials for commands, requiring users to look elsewhere for thorough understanding.
• Potential for Frustration
  Beginners might find some challenges too difficult, which could lead to frustration without adequate guidance or support.
• Internet Dependency
  An active internet connection is required to access the challenges, which may not be convenient for users with limited connectivity.

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

• Day 21 - What next?

  To get crazy fast in the command line, try Command Line Challenge, practicelinux.com, learnshell.org and commandlinefu.com. Source: almost 3 years ago

• The Unix Game

  I put something together very similar to this, https://cmdchallenge.com that I like a bit better because it has console input. There is also a Christmas edition "12 days of shell" https://12days.cmdchallenge.com that is more like a... - Source: Hacker News / about 3 years ago

• Openmoji

  Nice to see this posted on HN! A while back ago I used them for the design of a site a built https://cmdchallenge.com/ which gives it a nice feel of achievement badges without using standard unicode characters that may look different... - Source: Hacker News / about 3 years 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