DEV Community

Cover image for Collaborative Coding Adventures: Insights from Lab 1
Bhavik Mistry
Bhavik Mistry

Posted on

Collaborative Coding Adventures: Insights from Lab 1

Hello Everyone!

I'm pleased to talk about my recent experience in Lab 1 of our course, when we started a group coding adventure. Finding a partner, working closely with them, and carefully reviewing each other's project files were all required for this assignment in order to spot and resolve any problems that may have arisen. Let's get into the specifics of this eye-opening encounter.

Partnering Up: The Quest for Collaboration

In this lab I find a partner from a Slack channel where he send his GitHub repo link for review and I directly message that person on slack and we started collaborating.

Testing and Reviewing

It might be enlightening to test and review someone else's code. It's similar to getting a sneak preview of someone else's creative process and learning about the genius and difficulties that lie underneath. I have review the code of 2 peoples and created issues that I found in their project.
The issues that I have created were:

  1. Windows issue related to pathname

  2. Regarding updating the "How to run part in README.md" file

  3. The compile command given in README.md file is not working properly

  4. [The command for running the server is not working properly](https://github.com/sshah135/Converter/issues/5

1. Windows issue related to pathname
When I was trying to clone his repository I came across the error given below:
error: invalid path 'examples/What do API Keys REALLY do?.txt'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/

The working tree (the actual files and folders from the repository), however, cannot be checked out due to an error. According to the specific error notice, the repository contains a file with the name "examples/What do API Keys REALLY do?.txt" that is a "invalid path." Git is encountering a fatal error because it is unable to correctly check out the working tree due to this erroneous path.
And the issue was resolve when he removes the ? from the file name.

2. Regarding updating the "How to run part in README.md" file
When I saw the README.md file the "How to run part" has some information that are not correct so writer assisted her to update the part.
The below was the solution given by me:

git clone https://github.com/yourusername/text-to-html-converter.git
Enter fullscreen mode Exit fullscreen mode

command to

git clone https://github.com/sshah135/Converter.git
Enter fullscreen mode Exit fullscreen mode

Then do:

cd Converter
Enter fullscreen mode Exit fullscreen mode

image

Receiving Feedback: A Humbling Experience

It was helpful to have another person go through my code. II received constructive feedback that helped me become aware of previously unappreciated opportunities for improvement. Being able to see my work from another person's point of view was both humbling and inspiring.
I later resolved all the issues raised by my partner, ensuring the project's progress.

Key Takeaways:

This testing and reviewing procedure taught me numerous crucial insights, including:

  • The significance of precise documentation and discussion in team initiatives.

  • How to go into code review with a positive attitude and an open mind.

  • The importance of best practices and code uniformity.

In conclusion, Lab 1 was more than simply a task; it was a chance for development on both a personal and professional level.

Top comments (0)