From 3a464b2022fa416e0eb7cfef0be9f96c807eaaac Mon Sep 17 00:00:00 2001 From: VLADISLAV NACHIKOV Date: Fri, 9 May 2025 12:00:13 +0200 Subject: [PATCH 1/2] Update README.md Add link to DRY principle and modular code section in Week 1 README cause it might be helpful for new guys, and it also inside QA session --- Week1/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Week1/README.md b/Week1/README.md index ae62329..b0fac11 100644 --- a/Week1/README.md +++ b/Week1/README.md @@ -35,7 +35,7 @@ This week we are going to go a little deeper and get some extra building blocks You now have all of the basic building blocks that form the basis of all code! You will undoubtedly already have encountered the difficulty of reading code, and combining everything this week will make it even more difficult to follow. It is a good idea to revisit the debugger section with this new knowledge [here](https://study.hackyourfuture.net/#/tools/debuggers). Although it is called debugging, a lot of the process of finding 'bugs' in your code is trying to understand what is happening in the code. So keep using the debugger to understand pieces of code that you are not 100% comfortable with yet! -This is also the week we are going to start learning about best practices surrounding programming. These are general rules programmers follow so that code remains readable for others. The first will be about naming conventions, read more about that [here](https://study.hackyourfuture.net/#/programming/naming-conventions) and try to make it a habit to follow them. +This is also the week we are going to start learning about best practices surrounding programming. These are general rules programmers follow so that code remains readable for others. The first will be about naming conventions, read more about that [here](https://study.hackyourfuture.net/#/programming/naming-conventions) and try to make it a habit to follow them. And yeah, don't forget to make your code ["dry"](https://hackyourfuture.github.io/study/#/programming/dont-repeat-yourself?id=_2-modular-code) Lastly we want to introduce the first steps to testing code. Let's first have a look at what software testing is and why we do it [here](https://www.ministryoftesting.com/articles/e463d4ba?s_id=14519957). The simplest form of testing is using assertions, have a look what that is [here](https://study.hackyourfuture.net/#/testing/assertion), we will introduce this more in your assignment so you will see how it works. From f5b7b17e79eab9647a5f8a0f3e3beed0906d3dc6 Mon Sep 17 00:00:00 2001 From: Rohini Patil Date: Tue, 26 Aug 2025 14:28:02 +0200 Subject: [PATCH 2/2] Update hand-in-assignments-guide.md Updated repo name from Assignment-CohortXX to JavaScript-CohortXX --- hand-in-assignments-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hand-in-assignments-guide.md b/hand-in-assignments-guide.md index cd4154f..d3ac6d1 100644 --- a/hand-in-assignments-guide.md +++ b/hand-in-assignments-guide.md @@ -12,7 +12,7 @@ Watch the video (by clicking the image) or go through the following walk-through ### 1.1 One Time Only (start of every module) -1. Create a [fork](https://help.github.com/en/articles/fork-a-repo) of the assignment module repository. For JavaScript (as well as the next 2 modules), the assignment module repository is `https://www.github.com/HackYourAssignment/Assignment-cohortXX` where XX is your cohort number. You do this by using the `fork` option on the top right. +1. Create a [fork](https://help.github.com/en/articles/fork-a-repo) of the assignment module repository. For JavaScript (as well as the next 2 modules), the assignment module repository is `https://www.github.com/HackYourAssignment/JavaScript-cohortXX` where XX is your cohort number. You do this by using the `fork` option on the top right. 2. Navigate to the URL of the cloned repository (it should be in your personal GitHub account, under "repositories"). 3. Clone the repository, using SSH[1], to your local machine. You can do this by typing in `git clone ` in the command line. 4. On your local machine, navigate to the folder using the command line. @@ -27,7 +27,7 @@ Watch the video (by clicking the image) or go through the following walk-through 4. Once you're finished, add your assignment to a commit. There will be some test and config files added by the test runner, this is expected and should be added! 5. Create the commit (`git commit`). Make the commit message meaningful, for example `Finished project for assignment week 3`. 6. Push the branch to your forked repository. -7. On the GitHub page of your forked repository, click on the `create pull request` button. Make sure the `base repository` is the `Assignment-cohortXX` repository, on branch `main`. +7. On the GitHub page of your forked repository, click on the `create pull request` button. Make sure the `base repository` is the `JavaScript-cohortXX` repository, on branch `main`. 8. Give the pull request a title in the same format as you used for the branch, e.g: `YOUR_NAME-w3-JavaScript`. 9. Submit the pull request from your forked repository branch into the `main` branch of the destination repository.